Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cab67375341a064303c93acf5f9c30b8916ef193c306f8b83524d6b2dca9d34

Tx prefix hash: a856f903b0e7696e203475cf3344dbe75cd389622607d4384f865b6f816dab1e
Tx public key: f41c9d0045eacea02b5bf1f1d3a2a07ec8663607d689e32ccad9d158985f4454
Timestamp: 1724365815 Timestamp [UCT]: 2024-08-22 22:30:15 Age [y:d:h:m:s]: 01:077:06:44:50
Block: 1093762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313674 RingCT/type: yes/0
Extra: 01f41c9d0045eacea02b5bf1f1d3a2a07ec8663607d689e32ccad9d158985f4454021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06168e8aa033952569dd06ae88e6ea7f3a71e153d9688c0ef02b1b94644f1a5b 0.600000000000 1568771 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": 1093772, "vin": [ { "gen": { "height": 1093762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06168e8aa033952569dd06ae88e6ea7f3a71e153d9688c0ef02b1b94644f1a5b" } } ], "extra": [ 1, 244, 28, 157, 0, 69, 234, 206, 160, 43, 91, 241, 241, 211, 162, 160, 126, 200, 102, 54, 7, 214, 137, 227, 44, 202, 217, 209, 88, 152, 95, 68, 84, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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