Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5615938a56e16f33856448e83221ba5c3f351095f68d8c86f34ef6ddc4d910ac

Tx prefix hash: 6789d4a513914c5a5794c18ebb77cc158cf7a61f4a3a80e5075d4178925ee0dd
Tx public key: e2e14a1266c533fb0ffbe09d79d251ee78e44421b342e153d4b08bf80319f9b2
Timestamp: 1703463943 Timestamp [UCT]: 2023-12-25 00:25:43 Age [y:d:h:m:s]: 01:364:19:49:33
Block: 920474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519622 RingCT/type: yes/0
Extra: 01e2e14a1266c533fb0ffbe09d79d251ee78e44421b342e153d4b08bf80319f9b202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a217a8be61d3df14e3232dd5bc1206b7a96c2684831efefaaf2189b7fa9f4485 0.600000000000 1378152 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": 920484, "vin": [ { "gen": { "height": 920474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a217a8be61d3df14e3232dd5bc1206b7a96c2684831efefaaf2189b7fa9f4485" } } ], "extra": [ 1, 226, 225, 74, 18, 102, 197, 51, 251, 15, 251, 224, 157, 121, 210, 81, 238, 120, 228, 68, 33, 179, 66, 225, 83, 212, 176, 139, 248, 3, 25, 249, 178, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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