Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdf2bee8d9f51593cb200eeb5f38d5c5c865e522be4008104a93b50c6d96612

Tx prefix hash: 6fbfe0ea900ca20d1f03ed6d4a0847d7618fad4d16dee2f897d8ce8e1c72035e
Tx public key: 3cc28e85d86eb15f1485c23f217bfc8c0c29cec0391c363446f0aa2bb569e8fb
Timestamp: 1735256341 Timestamp [UCT]: 2024-12-26 23:39:01 Age [y:d:h:m:s]: 00:098:16:20:45
Block: 1183908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70327 RingCT/type: yes/0
Extra: 013cc28e85d86eb15f1485c23f217bfc8c0c29cec0391c363446f0aa2bb569e8fb021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 227e143335f42451fb19fbbec161f72a5c9c02e0cc7e53c592d644c6e6fc7010 0.600000000000 1670357 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": 1183918, "vin": [ { "gen": { "height": 1183908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "227e143335f42451fb19fbbec161f72a5c9c02e0cc7e53c592d644c6e6fc7010" } } ], "extra": [ 1, 60, 194, 142, 133, 216, 110, 177, 95, 20, 133, 194, 63, 33, 123, 252, 140, 12, 41, 206, 192, 57, 28, 54, 52, 70, 240, 170, 43, 181, 105, 232, 251, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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