Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8e02854061a80ea8576a10e79012ed118bbab61c805d055a4c269b75d397891

Tx prefix hash: 6bd533b64959ca755122b83f1ea54b88c9419fd115a18314df8c94364657b800
Tx public key: b5ba6a931e1b5024d6c2aa7915bfe9888840f531ca6d17c72ebbc6cf6d687c2c
Timestamp: 1734387610 Timestamp [UCT]: 2024-12-16 22:20:10 Age [y:d:h:m:s]: 00:093:01:07:00
Block: 1176745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66289 RingCT/type: yes/0
Extra: 01b5ba6a931e1b5024d6c2aa7915bfe9888840f531ca6d17c72ebbc6cf6d687c2c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f27abdadbe6ebd921b7ba16b87b384a205f5ac6f22e4a3610889c848fa82e79 0.600000000000 1663104 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": 1176755, "vin": [ { "gen": { "height": 1176745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f27abdadbe6ebd921b7ba16b87b384a205f5ac6f22e4a3610889c848fa82e79" } } ], "extra": [ 1, 181, 186, 106, 147, 30, 27, 80, 36, 214, 194, 170, 121, 21, 191, 233, 136, 136, 64, 245, 49, 202, 109, 23, 199, 46, 187, 198, 207, 109, 104, 124, 44, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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