Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22383983e1dc3fb8632f576589d19bf7042abf6b7b541ba445ce14392e3ed471

Tx prefix hash: 40aa97fa71ecc51fda142b61e21c379a600962e8ab9f574b89a4ed931d1051e2
Tx public key: f48836a769d25f3d0577942b26b114b1883d5c3bd7ab1d2bf42119ceb9e92c8d
Timestamp: 1720751836 Timestamp [UCT]: 2024-07-12 02:37:16 Age [y:d:h:m:s]: 01:131:05:41:47
Block: 1063798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352315 RingCT/type: yes/0
Extra: 01f48836a769d25f3d0577942b26b114b1883d5c3bd7ab1d2bf42119ceb9e92c8d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538f40302d81f03cc16c3e2a974833401453efad692c52a43654b808056b9ff7 0.600000000000 1534315 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": 1063808, "vin": [ { "gen": { "height": 1063798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538f40302d81f03cc16c3e2a974833401453efad692c52a43654b808056b9ff7" } } ], "extra": [ 1, 244, 136, 54, 167, 105, 210, 95, 61, 5, 119, 148, 43, 38, 177, 20, 177, 136, 61, 92, 59, 215, 171, 29, 43, 244, 33, 25, 206, 185, 233, 44, 141, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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