Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e3845a25568ff16f7ba8cd543f65e1b290c0ea4af081df10b5d5da6fe5e705a

Tx prefix hash: 595a7854efd7053cf54d9be2360c2d812c305090476c36b786ac7c782c7ae892
Tx public key: 04365c222ca7aa1db51f2dc92cef05dd272c7ab8feecb433d026fb29491fa628
Timestamp: 1711807269 Timestamp [UCT]: 2024-03-30 14:01:09 Age [y:d:h:m:s]: 01:078:15:21:09
Block: 989658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317082 RingCT/type: yes/0
Extra: 0104365c222ca7aa1db51f2dc92cef05dd272c7ab8feecb433d026fb29491fa6280211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee7106d151d02d7f58209cbc641bbfbe8d7f62bc95761350caf3d71200307cff 0.600000000000 1449976 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": 989668, "vin": [ { "gen": { "height": 989658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee7106d151d02d7f58209cbc641bbfbe8d7f62bc95761350caf3d71200307cff" } } ], "extra": [ 1, 4, 54, 92, 34, 44, 167, 170, 29, 181, 31, 45, 201, 44, 239, 5, 221, 39, 44, 122, 184, 254, 236, 180, 51, 208, 38, 251, 41, 73, 31, 166, 40, 2, 17, 0, 0, 0, 8, 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