Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d2ebdb207067d03fd87b67a8fb037dd1944b0ada0d1014676c5fbf3eefbd42

Tx prefix hash: b1c5557cf6b3c284e06862f36b9d2732d4ee64d6b76b52326bad471f54863683
Tx public key: 619bed4459b623e8036619113a00831727a2df6227661bb4f5bf93f08956ea2d
Timestamp: 1719551872 Timestamp [UCT]: 2024-06-28 05:17:52 Age [y:d:h:m:s]: 01:134:08:17:02
Block: 1053840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354556 RingCT/type: yes/0
Extra: 01619bed4459b623e8036619113a00831727a2df6227661bb4f5bf93f08956ea2d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c344b55c5d7983007f5e54ca71c505af5f5a599225ba70b3d861e600a43709 0.600000000000 1524191 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": 1053850, "vin": [ { "gen": { "height": 1053840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c344b55c5d7983007f5e54ca71c505af5f5a599225ba70b3d861e600a43709" } } ], "extra": [ 1, 97, 155, 237, 68, 89, 182, 35, 232, 3, 102, 25, 17, 58, 0, 131, 23, 39, 162, 223, 98, 39, 102, 27, 180, 245, 191, 147, 240, 137, 86, 234, 45, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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