Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8a2f46dea260cf87e69ec1328838f290bb13883b8b3e064000adfbdc955dbe

Tx prefix hash: b8aa58bae73f4cfb1350ccc04e9d2d45744a0a3aa74ac2902954b42df7d79f0e
Tx public key: 5dddd19d1d0f4696f639def218b14ee6aa7e7d91c893f55bff37b5c917dee8f1
Timestamp: 1714372380 Timestamp [UCT]: 2024-04-29 06:33:00 Age [y:d:h:m:s]: 01:039:20:13:33
Block: 1010900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289432 RingCT/type: yes/0
Extra: 015dddd19d1d0f4696f639def218b14ee6aa7e7d91c893f55bff37b5c917dee8f10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9e9d1ee4ff8427515bf6f108c83f838eed3e0ba0f141d8122e0ad6fd94f955 0.600000000000 1472978 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": 1010910, "vin": [ { "gen": { "height": 1010900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9e9d1ee4ff8427515bf6f108c83f838eed3e0ba0f141d8122e0ad6fd94f955" } } ], "extra": [ 1, 93, 221, 209, 157, 29, 15, 70, 150, 246, 57, 222, 242, 24, 177, 78, 230, 170, 126, 125, 145, 200, 147, 245, 91, 255, 55, 181, 201, 23, 222, 232, 241, 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