Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87734eb97d5c05c6d27b428632bf2fd512ceb90ab7ed32cb20068d9cc9b60d07

Tx prefix hash: b3893014f89046b1ee9085c08424026acad99aec6aac8f1ce154aec905a7b318
Tx public key: e1b134b59c0534a404659c1e3c4b73fd501db9c821dabb08d853efab2346266f
Timestamp: 1744870342 Timestamp [UCT]: 2025-04-17 06:12:22 Age [y:d:h:m:s]: 00:225:00:42:04
Block: 1263235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158565 RingCT/type: yes/0
Extra: 01e1b134b59c0534a404659c1e3c4b73fd501db9c821dabb08d853efab2346266f0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c697de616ee3e6266ecc6fcc6e70607b73c14d683a2d36e6f4814c2d48f9043 0.600000000000 1750420 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": 1263245, "vin": [ { "gen": { "height": 1263235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c697de616ee3e6266ecc6fcc6e70607b73c14d683a2d36e6f4814c2d48f9043" } } ], "extra": [ 1, 225, 177, 52, 181, 156, 5, 52, 164, 4, 101, 156, 30, 60, 75, 115, 253, 80, 29, 185, 200, 33, 218, 187, 8, 216, 83, 239, 171, 35, 70, 38, 111, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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