Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a1197d7ad5978b19d86703d975d9b713b731232b8c03416bcb3c30d250984a

Tx prefix hash: 1952cff90864c5f8e96b4612de34d9204cd35c5cbeae724f2533ff28e83df0c4
Tx public key: 2eb4ff9a82e3be8f42a8830adca84d371d36dcc3b3b52820c59428ca3cc04b5a
Timestamp: 1679449023 Timestamp [UCT]: 2023-03-22 01:37:03 Age [y:d:h:m:s]: 02:069:22:01:47
Block: 722268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571542 RingCT/type: yes/0
Extra: 012eb4ff9a82e3be8f42a8830adca84d371d36dcc3b3b52820c59428ca3cc04b5a0211000000035029cbac000000000000000000

1 output(s) for total of 2.482139403000 dcy

stealth address amount amount idx
00: 4b8a7336cb3243640d55535a14803398de15613c67f1cc1757f4e98054030f0c 2.482139403000 1167183 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": 722278, "vin": [ { "gen": { "height": 722268 } } ], "vout": [ { "amount": 2482139403, "target": { "key": "4b8a7336cb3243640d55535a14803398de15613c67f1cc1757f4e98054030f0c" } } ], "extra": [ 1, 46, 180, 255, 154, 130, 227, 190, 143, 66, 168, 131, 10, 220, 168, 77, 55, 29, 54, 220, 195, 179, 181, 40, 32, 197, 148, 40, 202, 60, 192, 75, 90, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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