Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdad35ae1dd4b1349a7c1a7cba55ec9831984e376a39b92cca6a7af0a6bc5b2

Tx prefix hash: 26beeb98148ee05c963e7ad5f5c83b692d8d88216300a3b605b556c95fa28d99
Tx public key: c5ec4b7e2675659ad365e80af4845d7ec2d99ff2ecd37998f3110afec932314d
Timestamp: 1706467499 Timestamp [UCT]: 2024-01-28 18:44:59 Age [y:d:h:m:s]: 01:068:14:29:35
Block: 945344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310109 RingCT/type: yes/0
Extra: 01c5ec4b7e2675659ad365e80af4845d7ec2d99ff2ecd37998f3110afec932314d02110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f72358021bdd7e6d3c5c6eb178b8e9fbbc611e071c7b9a0a12044b8ccca04494 0.600000000000 1403656 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": 945354, "vin": [ { "gen": { "height": 945344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72358021bdd7e6d3c5c6eb178b8e9fbbc611e071c7b9a0a12044b8ccca04494" } } ], "extra": [ 1, 197, 236, 75, 126, 38, 117, 101, 154, 211, 101, 232, 10, 244, 132, 93, 126, 194, 217, 159, 242, 236, 211, 121, 152, 243, 17, 10, 254, 201, 50, 49, 77, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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