Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 253504d96144379b7c9e646f0484dc236e25b26033ba5e0c0d74a47002cc8339

Tx prefix hash: 3cd04e7e46147f674689642e2c596ec04e33e65dec8c637ad8808c927742ec7f
Tx public key: 56d251e83049e9233e2c9c58c2619ebd683a547adcdc0530c4b18cd13719c318
Timestamp: 1700837282 Timestamp [UCT]: 2023-11-24 14:48:02 Age [y:d:h:m:s]: 01:347:07:21:42
Block: 898686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507084 RingCT/type: yes/0
Extra: 0156d251e83049e9233e2c9c58c2619ebd683a547adcdc0530c4b18cd13719c318021100000004faf35c9c000000000000000000

1 output(s) for total of 0.646070937000 dcy

stealth address amount amount idx
00: 3e4d2708eca2875f9f7cd85f55fd626b48297a713e4e42593192010e8297cf41 0.646070937000 1355117 of 0

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": 898696, "vin": [ { "gen": { "height": 898686 } } ], "vout": [ { "amount": 646070937, "target": { "key": "3e4d2708eca2875f9f7cd85f55fd626b48297a713e4e42593192010e8297cf41" } } ], "extra": [ 1, 86, 210, 81, 232, 48, 73, 233, 35, 62, 44, 156, 88, 194, 97, 158, 189, 104, 58, 84, 122, 220, 220, 5, 48, 196, 177, 140, 209, 55, 25, 195, 24, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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