Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 23605fe965fa9e7b0a5b6c47274a79aa5b089244a04631769c1684f1b2f0ca53

Tx prefix hash: e44d35fcd799a7f9de74ae30c91605105201acfd432c16b5c0c47711a4346dae
Tx public key: 65aa160155ea13766c49fa973cbc22672429a20ae0ab692f17c054e9c08e3a80
Timestamp: 1721305057 Timestamp [UCT]: 2024-07-18 12:17:37 Age [y:d:h:m:s]: 00:250:13:43:52
Block: 1068396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178970 RingCT/type: yes/0
Extra: 0165aa160155ea13766c49fa973cbc22672429a20ae0ab692f17c054e9c08e3a8002110000001991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aa656690c8a1a783d7b3f6638b583d510aa86b4def4ed1000cfc4dbcf081a24 0.600000000000 1539473 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1068406, "vin": [ { "gen": { "height": 1068396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aa656690c8a1a783d7b3f6638b583d510aa86b4def4ed1000cfc4dbcf081a24" } } ], "extra": [ 1, 101, 170, 22, 1, 85, 234, 19, 118, 108, 73, 250, 151, 60, 188, 34, 103, 36, 41, 162, 10, 224, 171, 105, 47, 23, 192, 84, 233, 192, 142, 58, 128, 2, 17, 0, 0, 0, 25, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8