Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597eaa727b86a0676ee9980713b823f6c43200586b1a92eeeb6e62308f42ef8e

Tx prefix hash: 5ec63088fcdc64df6a2dcbdc77c2a4e64f1334b293d4b227f14c4d3e402964fd
Tx public key: c8b0680a8d89739b78518c73385631026af1f1e6fb7c5f5161fca8d4e5e386d6
Timestamp: 1725854120 Timestamp [UCT]: 2024-09-09 03:55:20 Age [y:d:h:m:s]: 00:076:18:51:20
Block: 1106093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54904 RingCT/type: yes/0
Extra: 01c8b0680a8d89739b78518c73385631026af1f1e6fb7c5f5161fca8d4e5e386d602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c8957e7361bfbee47df467c2d937984981cad2a4dc072b5d605c902e2285be 0.600000000000 1583660 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": 1106103, "vin": [ { "gen": { "height": 1106093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c8957e7361bfbee47df467c2d937984981cad2a4dc072b5d605c902e2285be" } } ], "extra": [ 1, 200, 176, 104, 10, 141, 137, 115, 155, 120, 81, 140, 115, 56, 86, 49, 2, 106, 241, 241, 230, 251, 124, 95, 81, 97, 252, 168, 212, 229, 227, 134, 214, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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