Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbf5b7a9c5399f34a6b16c848daba24f9aa4987c383419d0daf0493801841ce

Tx prefix hash: 38249c9cbd99e0c13b1dcda2961ca99f0b555444366920a86a14c4a78d8186e1
Tx public key: f47a760739663eb14306822c9299246ea977fbb3fc8da7ec69d633f9469f1ba4
Timestamp: 1719859100 Timestamp [UCT]: 2024-07-01 18:38:20 Age [y:d:h:m:s]: 00:297:09:55:34
Block: 1056379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212530 RingCT/type: yes/0
Extra: 01f47a760739663eb14306822c9299246ea977fbb3fc8da7ec69d633f9469f1ba40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fb60c37a75e9691e7ec4103a07e3d2e628240c6a9a9d8f08c750bd81a8d6b9e 0.600000000000 1526792 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": 1056389, "vin": [ { "gen": { "height": 1056379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fb60c37a75e9691e7ec4103a07e3d2e628240c6a9a9d8f08c750bd81a8d6b9e" } } ], "extra": [ 1, 244, 122, 118, 7, 57, 102, 62, 177, 67, 6, 130, 44, 146, 153, 36, 110, 169, 119, 251, 179, 252, 141, 167, 236, 105, 214, 51, 249, 70, 159, 27, 164, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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