Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8bd0d6d0c87be334e615be6bc4957dd6c12f8b5132522f41a6565829c89776a

Tx prefix hash: c4e0431a61d3c7da0e94cd9cafed4505ccfa49d711df45119f10a7a064c23085
Tx public key: 409e268e9b68e95d6dca6841e8e7fc118045ffcc4f6a21e3d2cd8003ff72d49b
Timestamp: 1701504711 Timestamp [UCT]: 2023-12-02 08:11:51 Age [y:d:h:m:s]: 01:129:21:59:47
Block: 904214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354014 RingCT/type: yes/0
Extra: 01409e268e9b68e95d6dca6841e8e7fc118045ffcc4f6a21e3d2cd8003ff72d49b02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.619389214000 dcy

stealth address amount amount idx
00: dca6d08dc4f8745f7779b033ac027ae97ff3db3633ed0d3bcd6c2cad8a0ebfc6 0.619389214000 1360927 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": 904224, "vin": [ { "gen": { "height": 904214 } } ], "vout": [ { "amount": 619389214, "target": { "key": "dca6d08dc4f8745f7779b033ac027ae97ff3db3633ed0d3bcd6c2cad8a0ebfc6" } } ], "extra": [ 1, 64, 158, 38, 142, 155, 104, 233, 93, 109, 202, 104, 65, 232, 231, 252, 17, 128, 69, 255, 204, 79, 106, 33, 227, 210, 205, 128, 3, 255, 114, 212, 155, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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