Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073ae556565e057b430d6f2c3cdf982106ea07837f5fbf8e01fd6343dc6ea130

Tx prefix hash: 37b246c39d92290c2147481d4c79a9df278f50da8a85537f98edc03f1db242e6
Tx public key: 3c934b7cf981f88d6f2ca3aaa200a05b8028e0514bdbf1b3c7e542d907e68b84
Timestamp: 1702000683 Timestamp [UCT]: 2023-12-08 01:58:03 Age [y:d:h:m:s]: 01:080:05:10:57
Block: 908326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318444 RingCT/type: yes/0
Extra: 013c934b7cf981f88d6f2ca3aaa200a05b8028e0514bdbf1b3c7e542d907e68b84021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600259261000 dcy

stealth address amount amount idx
00: a2d006d65fa936aa8bc5ebb6fbffb1c93f7a080d73d304b5837863be12063ee7 0.600259261000 1365355 of 0

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": 908336, "vin": [ { "gen": { "height": 908326 } } ], "vout": [ { "amount": 600259261, "target": { "key": "a2d006d65fa936aa8bc5ebb6fbffb1c93f7a080d73d304b5837863be12063ee7" } } ], "extra": [ 1, 60, 147, 75, 124, 249, 129, 248, 141, 111, 44, 163, 170, 162, 0, 160, 91, 128, 40, 224, 81, 75, 219, 241, 179, 199, 229, 66, 217, 7, 230, 139, 132, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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