Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c23bb5ce101ec639c47b33b3db0f80ebadd51f1048648e920eae78b22aa21def

Tx prefix hash: 3a0b5c95d9cc236e9d47a11a0d5b406d3c75d688405c948f3dadeac4052129ec
Tx public key: 804ef3bfbcadf0d1e0fc3e29e400626cf4fab32a441908a21e4c343eb97bed9a
Timestamp: 1727180289 Timestamp [UCT]: 2024-09-24 12:18:09 Age [y:d:h:m:s]: 00:121:06:28:16
Block: 1117084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86670 RingCT/type: yes/0
Extra: 01804ef3bfbcadf0d1e0fc3e29e400626cf4fab32a441908a21e4c343eb97bed9a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cd536fcd71394cfd7d9b02d4fe6eca2984fd28c63796b536f53949235ddc91 0.600000000000 1597791 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": 1117094, "vin": [ { "gen": { "height": 1117084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cd536fcd71394cfd7d9b02d4fe6eca2984fd28c63796b536f53949235ddc91" } } ], "extra": [ 1, 128, 78, 243, 191, 188, 173, 240, 209, 224, 252, 62, 41, 228, 0, 98, 108, 244, 250, 179, 42, 68, 25, 8, 162, 30, 76, 52, 62, 185, 123, 237, 154, 2, 17, 0, 0, 0, 6, 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