Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef6c0cb286b828e2b5d75a568b7c7f32b279643224d84da6459e1c3ad7398c1

Tx prefix hash: e68ad438ee7ff3cb2970c8679fb820e6fe2252f5907d30b1416e06e6ca5df58d
Tx public key: 41e7e174b075c32a2aae1ed4dbf1c0b71dde4d179d24424dbb94bb12566b4f9c
Timestamp: 1695542013 Timestamp [UCT]: 2023-09-24 07:53:33 Age [y:d:h:m:s]: 02:044:09:08:00
Block: 854981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551354 RingCT/type: yes/0
Extra: 0141e7e174b075c32a2aae1ed4dbf1c0b71dde4d179d24424dbb94bb12566b4f9c0211000000034b8f5122000000000000000000

1 output(s) for total of 0.901764381000 dcy

stealth address amount amount idx
00: 4aca6365948fe1fdcb184b475bc671065666c0c23fc92bc21424b0503d53bca0 0.901764381000 1308977 of 0

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": 854991, "vin": [ { "gen": { "height": 854981 } } ], "vout": [ { "amount": 901764381, "target": { "key": "4aca6365948fe1fdcb184b475bc671065666c0c23fc92bc21424b0503d53bca0" } } ], "extra": [ 1, 65, 231, 225, 116, 176, 117, 195, 42, 42, 174, 30, 212, 219, 241, 192, 183, 29, 222, 77, 23, 157, 36, 66, 77, 187, 148, 187, 18, 86, 107, 79, 156, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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