Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18ecb82db39e0e74d6e444424b1591d67b42ba386b68dedd5405a846066a7260

Tx prefix hash: 835e4e08b00d45dc78c8451673927fdf64796019da0af03540d3bedb0518c958
Tx public key: 52a777e5e1fe5b217dc3d0b610aa5fc055629ed2d6541e1764a57ca236732c1f
Timestamp: 1711190301 Timestamp [UCT]: 2024-03-23 10:38:21 Age [y:d:h:m:s]: 00:358:10:53:20
Block: 984543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256281 RingCT/type: yes/0
Extra: 0152a777e5e1fe5b217dc3d0b610aa5fc055629ed2d6541e1764a57ca236732c1f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22769f6ee1178f1482a0b8985dcac128bf38e75c5ca527d2ba08ae5e8fb05ebc 0.600000000000 1444714 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": 984553, "vin": [ { "gen": { "height": 984543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22769f6ee1178f1482a0b8985dcac128bf38e75c5ca527d2ba08ae5e8fb05ebc" } } ], "extra": [ 1, 82, 167, 119, 229, 225, 254, 91, 33, 125, 195, 208, 182, 16, 170, 95, 192, 85, 98, 158, 210, 214, 84, 30, 23, 100, 165, 124, 162, 54, 115, 44, 31, 2, 17, 0, 0, 0, 4, 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