Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d24f81bd37dc8fb0d8e20f390b7a3154af243d89799c065e0ed1bfd2fe90002

Tx prefix hash: 2d130bf96eb76f29586c4637935cabec6d17619a4a49f009a4164d5a01d8e98f
Tx public key: 9609b34d63ac99db2c8b251269fcc31339b09352430b52b11b461c8f6c799367
Timestamp: 1710725462 Timestamp [UCT]: 2024-03-18 01:31:02 Age [y:d:h:m:s]: 01:049:17:14:15
Block: 980684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296518 RingCT/type: yes/0
Extra: 019609b34d63ac99db2c8b251269fcc31339b09352430b52b11b461c8f6c7993670211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae443ad7f316a1656fb7d0afa5d302b30b95b32bc6ec86e2b0c6b06f919ac5f4 0.600000000000 1440765 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": 980694, "vin": [ { "gen": { "height": 980684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae443ad7f316a1656fb7d0afa5d302b30b95b32bc6ec86e2b0c6b06f919ac5f4" } } ], "extra": [ 1, 150, 9, 179, 77, 99, 172, 153, 219, 44, 139, 37, 18, 105, 252, 195, 19, 57, 176, 147, 82, 67, 11, 82, 177, 27, 70, 28, 143, 108, 121, 147, 103, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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