Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d5c93a425574b6eca49c31a22e7b1089be10a25f89cf1e3502ce896f03d2a60

Tx prefix hash: aeed081fb20ce731e54b782fa0eed7652e32ca186a076f4f7b7e5dafed37e5ac
Tx public key: 038b54267da5b548737ec4a0acbbac4d2d36de8f18c7d83aedad9ccb090c9336
Timestamp: 1738007979 Timestamp [UCT]: 2025-01-27 19:59:39 Age [y:d:h:m:s]: 00:297:18:43:08
Block: 1206444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210570 RingCT/type: yes/0
Extra: 01038b54267da5b548737ec4a0acbbac4d2d36de8f18c7d83aedad9ccb090c933602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38d90f07d7cad3de2e8b418df2a489a2267596315f42d619b43132439adabc4 0.600000000000 1693149 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": 1206454, "vin": [ { "gen": { "height": 1206444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38d90f07d7cad3de2e8b418df2a489a2267596315f42d619b43132439adabc4" } } ], "extra": [ 1, 3, 139, 84, 38, 125, 165, 181, 72, 115, 126, 196, 160, 172, 187, 172, 77, 45, 54, 222, 143, 24, 199, 216, 58, 237, 173, 156, 203, 9, 12, 147, 54, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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