Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e55af8bd31701e75373fd135ad324cd08de47d1d938a85a4f8cf183d3ba9318

Tx prefix hash: b2362819cdc763d4d118a9bed67f2cb4dc59ac74655740dfd08a6922dd9f23e5
Tx public key: e6b009429172a69860256192368d982c1a9e3270b60f0497cd7a5c96ab53be6e
Timestamp: 1705657947 Timestamp [UCT]: 2024-01-19 09:52:27 Age [y:d:h:m:s]: 01:148:16:54:29
Block: 938622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367336 RingCT/type: yes/0
Extra: 01e6b009429172a69860256192368d982c1a9e3270b60f0497cd7a5c96ab53be6e0211000000137a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 306d5115593cddf3abe762b4bb3cfb442165bf3fa75c7a05f1143af1a06a9f3f 0.600000000000 1396692 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": 938632, "vin": [ { "gen": { "height": 938622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "306d5115593cddf3abe762b4bb3cfb442165bf3fa75c7a05f1143af1a06a9f3f" } } ], "extra": [ 1, 230, 176, 9, 66, 145, 114, 166, 152, 96, 37, 97, 146, 54, 141, 152, 44, 26, 158, 50, 112, 182, 15, 4, 151, 205, 122, 92, 150, 171, 83, 190, 110, 2, 17, 0, 0, 0, 19, 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