Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b41de6f2143f18717f3bacffd593c6b89d65b50bb42a633c31673318bed31b

Tx prefix hash: 19c3b8622c9b50df96732a16b821a04bede6b334803e3964193723ab75dc6e36
Tx public key: 94b8806f587ec132c4e4d378c0555d89d13b7b4766fff56cd26b3f815acf2d3a
Timestamp: 1719536402 Timestamp [UCT]: 2024-06-28 01:00:02 Age [y:d:h:m:s]: 00:319:20:27:50
Block: 1053714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228577 RingCT/type: yes/0
Extra: 0194b8806f587ec132c4e4d378c0555d89d13b7b4766fff56cd26b3f815acf2d3a02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c3d453588f65b5cd9f589fe72418e5caf250a4622df4c6776d2a76613c10217 0.600000000000 1524063 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": 1053724, "vin": [ { "gen": { "height": 1053714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c3d453588f65b5cd9f589fe72418e5caf250a4622df4c6776d2a76613c10217" } } ], "extra": [ 1, 148, 184, 128, 111, 88, 126, 193, 50, 196, 228, 211, 120, 192, 85, 93, 137, 209, 59, 123, 71, 102, 255, 245, 108, 210, 107, 63, 129, 90, 207, 45, 58, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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