Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fee192e09b430c05d3616b674a73a66f75dccaaad99697d5b7b805e9cb12594

Tx prefix hash: b49051c942cc7c620f5d7b5bdfe1a41c5754741420c18d775b73c8a8c97bb442
Tx public key: 0c35b58893d8d86ed2c9c04a40bdd12cd9a2bccffaaf9f573b298a93916a1d62
Timestamp: 1720598911 Timestamp [UCT]: 2024-07-10 08:08:31 Age [y:d:h:m:s]: 00:281:09:33:22
Block: 1062531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201041 RingCT/type: yes/0
Extra: 010c35b58893d8d86ed2c9c04a40bdd12cd9a2bccffaaf9f573b298a93916a1d6202110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd569ee59add29a4d9200793cd9d121536b067a87a984543959f8e171a09098c 0.600000000000 1533036 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": 1062541, "vin": [ { "gen": { "height": 1062531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd569ee59add29a4d9200793cd9d121536b067a87a984543959f8e171a09098c" } } ], "extra": [ 1, 12, 53, 181, 136, 147, 216, 216, 110, 210, 201, 192, 74, 64, 189, 209, 44, 217, 162, 188, 207, 250, 175, 159, 87, 59, 41, 138, 147, 145, 106, 29, 98, 2, 17, 0, 0, 0, 15, 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