Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa80b101aea8f6f626e9cb6e6cc58bf829eba5a2c0df9191912e79fd9522834

Tx prefix hash: de5b08ab058f1d21b17810fcd74bb958ee065f32657c0b321128df846c9d94f7
Tx public key: 89ed115f1fa568de60336bcc1060608ff9dc2a4315d9786ee9308d4ebb613709
Timestamp: 1700899645 Timestamp [UCT]: 2023-11-25 08:07:25 Age [y:d:h:m:s]: 01:097:05:58:57
Block: 899199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330648 RingCT/type: yes/0
Extra: 0189ed115f1fa568de60336bcc1060608ff9dc2a4315d9786ee9308d4ebb6137090211000000014b8f5122000000000000000000

1 output(s) for total of 0.643547225000 dcy

stealth address amount amount idx
00: 7b9fa6d5acaf4ae951b3c05854117bf31f7befb4814091f7f3b5ea1e9742f90c 0.643547225000 1355644 of 0

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": 899209, "vin": [ { "gen": { "height": 899199 } } ], "vout": [ { "amount": 643547225, "target": { "key": "7b9fa6d5acaf4ae951b3c05854117bf31f7befb4814091f7f3b5ea1e9742f90c" } } ], "extra": [ 1, 137, 237, 17, 95, 31, 165, 104, 222, 96, 51, 107, 204, 16, 96, 96, 143, 249, 220, 42, 67, 21, 217, 120, 110, 233, 48, 141, 78, 187, 97, 55, 9, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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