Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8553fc41bf5a90a4c7b8e5e8a82c80b5a9483c4fbd5e5855a1b4a5ba725170a

Tx prefix hash: 8e2db4ab6fad67ac7ffbeb4d1346796e7123cb0bdf25a338b4125ca50ba3f049
Tx public key: e950d8f838cdbc0e5ce8c99c453565a34937fc65f3fa9d5fe0838026a8181d65
Timestamp: 1750664019 Timestamp [UCT]: 2025-06-23 07:33:39 Age [y:d:h:m:s]: 00:143:11:24:46
Block: 1310993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100424 RingCT/type: yes/0
Extra: 01e950d8f838cdbc0e5ce8c99c453565a34937fc65f3fa9d5fe0838026a8181d650211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d47b99319fb54813f2e4e68ba34b578dba6d7ab295a4f828af059e624cd7efa 0.600000000000 1798618 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": 1311003, "vin": [ { "gen": { "height": 1310993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d47b99319fb54813f2e4e68ba34b578dba6d7ab295a4f828af059e624cd7efa" } } ], "extra": [ 1, 233, 80, 216, 248, 56, 205, 188, 14, 92, 232, 201, 156, 69, 53, 101, 163, 73, 55, 252, 101, 243, 250, 157, 95, 224, 131, 128, 38, 168, 24, 29, 101, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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