Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 542ae7a4c96dfe4c903af2acf6b29aa03cec424b7d1020a16db9595ffacd6b4a

Tx prefix hash: e5a3bfa4531ade844b793a3d02db6355f52d5bed950ac4baca1db349c3440b30
Tx public key: 9bef8f8764e219f11355f776dbd057ceae257d34e5d71223a40f6f16bcfe6b23
Timestamp: 1727484340 Timestamp [UCT]: 2024-09-28 00:45:40 Age [y:d:h:m:s]: 00:195:22:12:00
Block: 1119602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139846 RingCT/type: yes/0
Extra: 019bef8f8764e219f11355f776dbd057ceae257d34e5d71223a40f6f16bcfe6b2302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f3a28d1294327e7c634f8029404abb6f7a06886c61868e781625498c3944ab 0.600000000000 1601221 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": 1119612, "vin": [ { "gen": { "height": 1119602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f3a28d1294327e7c634f8029404abb6f7a06886c61868e781625498c3944ab" } } ], "extra": [ 1, 155, 239, 143, 135, 100, 226, 25, 241, 19, 85, 247, 118, 219, 208, 87, 206, 174, 37, 125, 52, 229, 215, 18, 35, 164, 15, 111, 22, 188, 254, 107, 35, 2, 17, 0, 0, 0, 2, 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