Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fec518ad4e4bbdb19a25202dcc2051b15e4291befe867f9418c4b433ad76c90

Tx prefix hash: 872f13be7d335c69d98daf63cc47919b9e76c3e4b4ee74b56be0796207d47a97
Tx public key: 92bc31c6bfa54fd19f64c8c704035ff1ce99d7a5a66db59d974c953c06acc651
Timestamp: 1724337169 Timestamp [UCT]: 2024-08-22 14:32:49 Age [y:d:h:m:s]: 00:230:13:59:02
Block: 1093524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164652 RingCT/type: yes/0
Extra: 0192bc31c6bfa54fd19f64c8c704035ff1ce99d7a5a66db59d974c953c06acc651021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2c12efeea0f0e78ae78814608772bbd6c14db05a14d05581474d0ea5fd80a85 0.600000000000 1568485 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": 1093534, "vin": [ { "gen": { "height": 1093524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2c12efeea0f0e78ae78814608772bbd6c14db05a14d05581474d0ea5fd80a85" } } ], "extra": [ 1, 146, 188, 49, 198, 191, 165, 79, 209, 159, 100, 200, 199, 4, 3, 95, 241, 206, 153, 215, 165, 166, 109, 181, 157, 151, 76, 149, 60, 6, 172, 198, 81, 2, 17, 0, 0, 0, 2, 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