Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b87d3d7650be5444d5d76d586261dcf558fd28626a8b4b15c18a01de6bf737

Tx prefix hash: 2e536c0e5825afd84c085c08d097b5b67dff8e4a8c0ce14e6e2e6d83c8c3062d
Tx public key: d16daa76f7c176177292c21fa9b10453cd8cb28a58e44e89ef2a6d751ffb640e
Timestamp: 1733725874 Timestamp [UCT]: 2024-12-09 06:31:14 Age [y:d:h:m:s]: 00:111:03:52:12
Block: 1171255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79227 RingCT/type: yes/0
Extra: 01d16daa76f7c176177292c21fa9b10453cd8cb28a58e44e89ef2a6d751ffb640e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6ca33a77b79be5f6f7cfc00a256c33caa197c36aa4a1b364b86bf0eb399d6c 0.600000000000 1656994 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": 1171265, "vin": [ { "gen": { "height": 1171255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6ca33a77b79be5f6f7cfc00a256c33caa197c36aa4a1b364b86bf0eb399d6c" } } ], "extra": [ 1, 209, 109, 170, 118, 247, 193, 118, 23, 114, 146, 194, 31, 169, 177, 4, 83, 205, 140, 178, 138, 88, 228, 78, 137, 239, 42, 109, 117, 31, 251, 100, 14, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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