Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d3bcf07d9f67f5140231a703f10db7f5b487dc5af3d3a35d56c8d5e51c0928

Tx prefix hash: 1a03475a4433a23b8491419cdf3456330a7cba60da575b65c0e11d169abe1e23
Tx public key: ff51b0aedba0dc40c930861f464b88404687eaf3d6aa9766e51566ba512ecdf0
Timestamp: 1715520774 Timestamp [UCT]: 2024-05-12 13:32:54 Age [y:d:h:m:s]: 01:181:16:55:31
Block: 1020453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388445 RingCT/type: yes/0
Extra: 01ff51b0aedba0dc40c930861f464b88404687eaf3d6aa9766e51566ba512ecdf002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d5de053f301b0570b89ec02b89c5c685aa1cdb6538891a9e36017727014858 0.600000000000 1484526 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": 1020463, "vin": [ { "gen": { "height": 1020453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d5de053f301b0570b89ec02b89c5c685aa1cdb6538891a9e36017727014858" } } ], "extra": [ 1, 255, 81, 176, 174, 219, 160, 220, 64, 201, 48, 134, 31, 70, 75, 136, 64, 70, 135, 234, 243, 214, 170, 151, 102, 229, 21, 102, 186, 81, 46, 205, 240, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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