Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c82525b46ef553249812872b909ca45aabe8bec4ee25f9eae59da66a65c67b

Tx prefix hash: 67048ac4e677eeae60a38612fafe04f654a4b1473a9dabb1edccf85056146c25
Tx public key: d5aa09cffc477550d9b4965b28e1b1c3988f5ec06858c3d2b7d3094d6d4e1668
Timestamp: 1714646698 Timestamp [UCT]: 2024-05-02 10:44:58 Age [y:d:h:m:s]: 00:336:15:12:19
Block: 1013176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240622 RingCT/type: yes/0
Extra: 01d5aa09cffc477550d9b4965b28e1b1c3988f5ec06858c3d2b7d3094d6d4e16680211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2b59966534800b509526b171fffd59b1b2a121d6ae2688310414055d02030dc 0.600000000000 1475923 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": 1013186, "vin": [ { "gen": { "height": 1013176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2b59966534800b509526b171fffd59b1b2a121d6ae2688310414055d02030dc" } } ], "extra": [ 1, 213, 170, 9, 207, 252, 71, 117, 80, 217, 180, 150, 91, 40, 225, 177, 195, 152, 143, 94, 192, 104, 88, 195, 210, 183, 211, 9, 77, 109, 78, 22, 104, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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