Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a337f5754b48cc5e28c6a71237be3d6f151ef6361a0eea6368ff127340d73b

Tx prefix hash: f51a8bbce84490bddb7681072c72d36f8d27073e8c37e92154addd05cb937476
Tx public key: 9d62294d3c3c04c3ba722347d6b113ba483f9700b254c4ba39c012b2cbd5a6cf
Timestamp: 1710591035 Timestamp [UCT]: 2024-03-16 12:10:35 Age [y:d:h:m:s]: 01:058:14:31:42
Block: 979571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302874 RingCT/type: yes/0
Extra: 019d62294d3c3c04c3ba722347d6b113ba483f9700b254c4ba39c012b2cbd5a6cf0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb14bb5f711cc63d6fb847b0a9c56fbba5befab930949f72a7e8164ad50c3851 0.600000000000 1439608 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": 979581, "vin": [ { "gen": { "height": 979571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb14bb5f711cc63d6fb847b0a9c56fbba5befab930949f72a7e8164ad50c3851" } } ], "extra": [ 1, 157, 98, 41, 77, 60, 60, 4, 195, 186, 114, 35, 71, 214, 177, 19, 186, 72, 63, 151, 0, 178, 84, 196, 186, 57, 192, 18, 178, 203, 213, 166, 207, 2, 17, 0, 0, 0, 6, 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