Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206d780f225d56ac0d42a296103dbb9ca5e5103e626bd17323f3ab59fc87aa83

Tx prefix hash: af9f6dfb18977e5e8a2ec0898189d446c33f8a7d4fe59ab5e2a9aec33e82528d
Tx public key: da4b0123c79d2fd4161798db69cd9ebf5b7ca6d0528eecb8f8f6e3b73aa24751
Timestamp: 1725122282 Timestamp [UCT]: 2024-08-31 16:38:02 Age [y:d:h:m:s]: 00:237:15:33:54
Block: 1100016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169718 RingCT/type: yes/0
Extra: 01da4b0123c79d2fd4161798db69cd9ebf5b7ca6d0528eecb8f8f6e3b73aa24751021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a977ced88055b39d474333766290d864950c1bac4b7829a9ce281e54fcfd047 0.600000000000 1575987 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": 1100026, "vin": [ { "gen": { "height": 1100016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a977ced88055b39d474333766290d864950c1bac4b7829a9ce281e54fcfd047" } } ], "extra": [ 1, 218, 75, 1, 35, 199, 157, 47, 212, 22, 23, 152, 219, 105, 205, 158, 191, 91, 124, 166, 208, 82, 142, 236, 184, 248, 246, 227, 183, 58, 162, 71, 81, 2, 17, 0, 0, 0, 5, 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