Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8939c8f380049180e0c252d68429ec9904e7d2b00d8f7242cd8a4091572ff25f

Tx prefix hash: 58f0fde6c6387d0491e10f4c5de65bbc7cc111f551867f0b9cb2401e9e2e10c7
Tx public key: 27b19105c8e92fb83b36fd1653c7221d3ca7586acc3a92cf75efd64142538a7a
Timestamp: 1738271193 Timestamp [UCT]: 2025-01-30 21:06:33 Age [y:d:h:m:s]: 00:042:10:05:05
Block: 1208612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30343 RingCT/type: yes/0
Extra: 0127b19105c8e92fb83b36fd1653c7221d3ca7586acc3a92cf75efd64142538a7a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: def0d30b41815f57a990579a8a752b4ee8001e0252b2e76f3dbc91747467c007 0.600000000000 1695345 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": 1208622, "vin": [ { "gen": { "height": 1208612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "def0d30b41815f57a990579a8a752b4ee8001e0252b2e76f3dbc91747467c007" } } ], "extra": [ 1, 39, 177, 145, 5, 200, 233, 47, 184, 59, 54, 253, 22, 83, 199, 34, 29, 60, 167, 88, 106, 204, 58, 146, 207, 117, 239, 214, 65, 66, 83, 138, 122, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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