Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bdf1a0cc52edb07a21271c07c24f7caa5bb237ea99117badc84a754392fd692

Tx prefix hash: 2cfce7b939781a913d9b3ccc36e2f5f5a62dc3c95fac9629c78077f1365408c9
Tx public key: 586eb402f8dec18e3e0069773354d7384085b07287b1c507e5fa93ffe74f0e2c
Timestamp: 1764945255 Timestamp [UCT]: 2025-12-05 14:34:15 Age [y:d:h:m:s]: 00:034:04:20:27
Block: 1427030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24489 RingCT/type: yes/0
Extra: 01586eb402f8dec18e3e0069773354d7384085b07287b1c507e5fa93ffe74f0e2c02110000000870609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1097d3a0a1c25326e239a8aaf8c9ab5be089e0cb5d60380ff219131e94b9b136 0.600000000000 1915729 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": 1427040, "vin": [ { "gen": { "height": 1427030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1097d3a0a1c25326e239a8aaf8c9ab5be089e0cb5d60380ff219131e94b9b136" } } ], "extra": [ 1, 88, 110, 180, 2, 248, 222, 193, 142, 62, 0, 105, 119, 51, 84, 215, 56, 64, 133, 176, 114, 135, 177, 197, 7, 229, 250, 147, 255, 231, 79, 14, 44, 2, 17, 0, 0, 0, 8, 112, 96, 157, 3, 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