Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b1af249ad4b818ba5d5b0d201f395ee10926b31235a3af85a767f274c35348e

Tx prefix hash: dcc168cd4b3ee673e5731ecec65dec1636782c101d0a390a646a2886541ed44c
Tx public key: 716b250d8b9403d62db4b9b634645752b084c8d8e85f5b43d32e82a78a1d6efb
Timestamp: 1731195684 Timestamp [UCT]: 2024-11-09 23:41:24 Age [y:d:h:m:s]: 00:187:12:41:57
Block: 1150292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133871 RingCT/type: yes/0
Extra: 01716b250d8b9403d62db4b9b634645752b084c8d8e85f5b43d32e82a78a1d6efb021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 439f1acac8f567cd1da527fc2287f0bf2dccd06bb4e29acdba6b996860d84436 0.600000000000 1635561 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": 1150302, "vin": [ { "gen": { "height": 1150292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "439f1acac8f567cd1da527fc2287f0bf2dccd06bb4e29acdba6b996860d84436" } } ], "extra": [ 1, 113, 107, 37, 13, 139, 148, 3, 214, 45, 180, 185, 182, 52, 100, 87, 82, 176, 132, 200, 216, 232, 95, 91, 67, 211, 46, 130, 167, 138, 29, 110, 251, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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