Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11781c98ac32a08d966600d2c5b9707b3d2638b3f9c93d5c4c0bee24b1dbbd49

Tx prefix hash: 7132df96f57336ed56eb283eed2503a6033e0bf8bd4bef2a1ff5dd5702b609a0
Tx public key: dfb7e8f5ab2726a890a7ac7306b1d09062a288da31205d98b8d8fc75f67816f6
Timestamp: 1721171210 Timestamp [UCT]: 2024-07-16 23:06:50 Age [y:d:h:m:s]: 00:264:14:18:31
Block: 1067278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189009 RingCT/type: yes/0
Extra: 01dfb7e8f5ab2726a890a7ac7306b1d09062a288da31205d98b8d8fc75f67816f602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f7a238cd1373b3bdd14702f9c0219931ae1b29449e1f9ca683d338eee888cdb 0.600000000000 1538051 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": 1067288, "vin": [ { "gen": { "height": 1067278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f7a238cd1373b3bdd14702f9c0219931ae1b29449e1f9ca683d338eee888cdb" } } ], "extra": [ 1, 223, 183, 232, 245, 171, 39, 38, 168, 144, 167, 172, 115, 6, 177, 208, 144, 98, 162, 136, 218, 49, 32, 93, 152, 184, 216, 252, 117, 246, 120, 22, 246, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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