Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4048a673e0f0aabfe3c8bf18d6f599bfb2b9fd1831b0dd68633c23eced34539f

Tx prefix hash: d8325c07aaf3248beea2e9fc241d55b3abb7e614865318c975de5cf9837ea3c6
Tx public key: 8d9b42c4f4a40cda037a404aaefbf830ebe4b6479da8e1ccf0f4d21d6ac4b147
Timestamp: 1737591566 Timestamp [UCT]: 2025-01-23 00:19:26 Age [y:d:h:m:s]: 00:145:18:14:24
Block: 1203203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103914 RingCT/type: yes/0
Extra: 018d9b42c4f4a40cda037a404aaefbf830ebe4b6479da8e1ccf0f4d21d6ac4b14702110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df5af4156bfc3289d449266b5765d39734cafdf2efc359e3b0324aa264cd4aea 0.600000000000 1689876 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": 1203213, "vin": [ { "gen": { "height": 1203203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df5af4156bfc3289d449266b5765d39734cafdf2efc359e3b0324aa264cd4aea" } } ], "extra": [ 1, 141, 155, 66, 196, 244, 164, 12, 218, 3, 122, 64, 74, 174, 251, 248, 48, 235, 228, 182, 71, 157, 168, 225, 204, 240, 244, 210, 29, 106, 196, 177, 71, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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