Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2df3b265aa311a8c590b6d6ac47928a92096a6b3c368f2926b9520be3837941

Tx prefix hash: 84ed6ea36f8d6e2c4ebe72f9141c66ed83c1329c1e0a09d441e2791e551a8e93
Tx public key: 57378ca50c73daa01faf869df85aadd1891b88618f53857da3c3d5919f2a06f3
Timestamp: 1713187770 Timestamp [UCT]: 2024-04-15 13:29:30 Age [y:d:h:m:s]: 01:031:07:03:40
Block: 1001072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283336 RingCT/type: yes/0
Extra: 0157378ca50c73daa01faf869df85aadd1891b88618f53857da3c3d5919f2a06f30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5451e5031e68fd0dd4c48bef06b105265574ed62a9ce5c01d2f4d14a9dcb91 0.600000000000 1461574 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": 1001082, "vin": [ { "gen": { "height": 1001072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5451e5031e68fd0dd4c48bef06b105265574ed62a9ce5c01d2f4d14a9dcb91" } } ], "extra": [ 1, 87, 55, 140, 165, 12, 115, 218, 160, 31, 175, 134, 157, 248, 90, 173, 209, 137, 27, 136, 97, 143, 83, 133, 125, 163, 195, 213, 145, 159, 42, 6, 243, 2, 17, 0, 0, 0, 4, 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