Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22107f8d5789fd015d8892b312ef526e35a6ca13bf27c7d65c72fe9b88bc1b52

Tx prefix hash: 5f056ec562d1dce501d02faa291e99170043f2cf4e2f846c86953156e5ffd89b
Tx public key: 04021386d921be2facd241aaf4ad007f28e6f3e4783c5823f66c059c9ad42970
Timestamp: 1702290988 Timestamp [UCT]: 2023-12-11 10:36:28 Age [y:d:h:m:s]: 01:031:20:09:19
Block: 910740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284119 RingCT/type: yes/0
Extra: 0104021386d921be2facd241aaf4ad007f28e6f3e4783c5823f66c059c9ad4297002110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c7665b055384ddc1feae1788d2dfd2711dd01f1088ba29b344873ac3fd13ddd 0.600000000000 1367907 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": 910750, "vin": [ { "gen": { "height": 910740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c7665b055384ddc1feae1788d2dfd2711dd01f1088ba29b344873ac3fd13ddd" } } ], "extra": [ 1, 4, 2, 19, 134, 217, 33, 190, 47, 172, 210, 65, 170, 244, 173, 0, 127, 40, 230, 243, 228, 120, 60, 88, 35, 246, 108, 5, 156, 154, 212, 41, 112, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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