Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d0c1872f8e45c6d10f82e5d3ac3430dca0ac9d4494f20cb1349012ee4d9349c

Tx prefix hash: 09b71f7b2f65d213d55e7e9b3458f5a8e65668c4f26ed4ef6044422cc8a9b090
Tx public key: 478b5892c42b00717d1f943fa0bd8e64d27920726c618fa2cc22f1bee9543aa7
Timestamp: 1736139951 Timestamp [UCT]: 2025-01-06 05:05:51 Age [y:d:h:m:s]: 00:090:23:15:36
Block: 1191242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64774 RingCT/type: yes/0
Extra: 01478b5892c42b00717d1f943fa0bd8e64d27920726c618fa2cc22f1bee9543aa70211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032a3dd6bbbfc9cfae42a27dc831c1f45df3e44c8d9f3eb5796ae9873bb4ce23 0.600000000000 1677765 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": 1191252, "vin": [ { "gen": { "height": 1191242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032a3dd6bbbfc9cfae42a27dc831c1f45df3e44c8d9f3eb5796ae9873bb4ce23" } } ], "extra": [ 1, 71, 139, 88, 146, 196, 43, 0, 113, 125, 31, 148, 63, 160, 189, 142, 100, 210, 121, 32, 114, 108, 97, 143, 162, 204, 34, 241, 190, 233, 84, 58, 167, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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