Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6efd8e1abb025662036f4d9dd16dcb63d052e2458adf8ec59964ee3a99fa15bd

Tx prefix hash: 2d23805c7d7510adaa87f3b19cff5823b95c16857997e767d115c4f5ad111f97
Tx public key: bc4ec86e9bc50f6f4911e8d4026bab46da9ff1f65771d3f1d5d267c534cff73b
Timestamp: 1714265470 Timestamp [UCT]: 2024-04-28 00:51:10 Age [y:d:h:m:s]: 00:354:20:01:42
Block: 1010005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253653 RingCT/type: yes/0
Extra: 01bc4ec86e9bc50f6f4911e8d4026bab46da9ff1f65771d3f1d5d267c534cff73b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b61cdaee3e58804825d268df069b7914f75de8394b0652bb7b224069bd12db81 0.600000000000 1471835 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": 1010015, "vin": [ { "gen": { "height": 1010005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b61cdaee3e58804825d268df069b7914f75de8394b0652bb7b224069bd12db81" } } ], "extra": [ 1, 188, 78, 200, 110, 155, 197, 15, 111, 73, 17, 232, 212, 2, 107, 171, 70, 218, 159, 241, 246, 87, 113, 211, 241, 213, 210, 103, 197, 52, 207, 247, 59, 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