Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34a9d7df7e2aead6cd8383b1e6a5c0f57c824c851007e25ca7421eaf806ccb3

Tx prefix hash: 462c656a79d26dcb2bb3eac2ebc6f0738d0a91ef1503e83b2d6f4c33f16d261f
Tx public key: 06f3e60abea5fa1ff6d50a9c6239759f9460f298e8deb45a19c14307640c5340
Timestamp: 1713694457 Timestamp [UCT]: 2024-04-21 10:14:17 Age [y:d:h:m:s]: 00:350:04:46:51
Block: 1005281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250333 RingCT/type: yes/0
Extra: 0106f3e60abea5fa1ff6d50a9c6239759f9460f298e8deb45a19c14307640c534002110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45a55a91db7c68af0d712fdc6a8e60fb1af8d7c484c022b6e54db4f3a144c749 0.600000000000 1465867 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": 1005291, "vin": [ { "gen": { "height": 1005281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45a55a91db7c68af0d712fdc6a8e60fb1af8d7c484c022b6e54db4f3a144c749" } } ], "extra": [ 1, 6, 243, 230, 10, 190, 165, 250, 31, 246, 213, 10, 156, 98, 57, 117, 159, 148, 96, 242, 152, 232, 222, 180, 90, 25, 193, 67, 7, 100, 12, 83, 64, 2, 17, 0, 0, 0, 12, 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