Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5057c2316fb115647faa6d8fdd23c8ae4ff4358edb8ce0959912a5345ccd5554

Tx prefix hash: 2b8080e93532df4f746034e8fa630624b3cef9d9399a0f5ec7b08c9892f580f9
Tx public key: 3f1ff8ad8598d7542e61a2000cc439cfde963aea066fd8bb71cb2bd040c44d81
Timestamp: 1712686147 Timestamp [UCT]: 2024-04-09 18:09:07 Age [y:d:h:m:s]: 00:342:15:55:12
Block: 996904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245004 RingCT/type: yes/0
Extra: 013f1ff8ad8598d7542e61a2000cc439cfde963aea066fd8bb71cb2bd040c44d810211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2fcaf994ccb95994e4a54c14b120ac1580b8f2f664a86fedaca73a8d89dfdcc 0.600000000000 1457332 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": 996914, "vin": [ { "gen": { "height": 996904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2fcaf994ccb95994e4a54c14b120ac1580b8f2f664a86fedaca73a8d89dfdcc" } } ], "extra": [ 1, 63, 31, 248, 173, 133, 152, 215, 84, 46, 97, 162, 0, 12, 196, 57, 207, 222, 150, 58, 234, 6, 111, 216, 187, 113, 203, 43, 208, 64, 196, 77, 129, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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