Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55ca6bdc4dfa1ec553a5b964db5e76b576a71153f42e6511d447dabb84054e52

Tx prefix hash: 003b0894290e3c3be5bfb28d6f6fe209ae318ad5925c40a6f9b37df0a53c1eca
Tx public key: a3025985ca1fd268efd9a669a4964bfea48a6403b66ff24d3c4900473403f040
Timestamp: 1705623143 Timestamp [UCT]: 2024-01-19 00:12:23 Age [y:d:h:m:s]: 01:072:08:57:55
Block: 938344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312818 RingCT/type: yes/0
Extra: 01a3025985ca1fd268efd9a669a4964bfea48a6403b66ff24d3c4900473403f0400211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5ef2c0b878c06919fa621abc076c2de5032887013073666322622f982bfb2f 0.600000000000 1396414 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": 938354, "vin": [ { "gen": { "height": 938344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5ef2c0b878c06919fa621abc076c2de5032887013073666322622f982bfb2f" } } ], "extra": [ 1, 163, 2, 89, 133, 202, 31, 210, 104, 239, 217, 166, 105, 164, 150, 75, 254, 164, 138, 100, 3, 182, 111, 242, 77, 60, 73, 0, 71, 52, 3, 240, 64, 2, 17, 0, 0, 0, 2, 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