Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a728e1b65ea4a1bf521102b7908af13fa475fbbfb841a1f67600e13b7930de

Tx prefix hash: 358e4421c21d45535d409a2e67b48eb692d063a7e693ab3f73134c2f176f8190
Tx public key: c73d509cfafc5d294f55abf3f3fa9266156d446a0da04dd89ec27ea19eb7901a
Timestamp: 1750627397 Timestamp [UCT]: 2025-06-22 21:23:17 Age [y:d:h:m:s]: 00:220:19:28:52
Block: 1310693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155618 RingCT/type: yes/0
Extra: 01c73d509cfafc5d294f55abf3f3fa9266156d446a0da04dd89ec27ea19eb7901a021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a72f5226f1dc1fe92044abb417773b438c6192af0fe80f4a9325262d2cfa338 0.600000000000 1798316 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": 1310703, "vin": [ { "gen": { "height": 1310693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a72f5226f1dc1fe92044abb417773b438c6192af0fe80f4a9325262d2cfa338" } } ], "extra": [ 1, 199, 61, 80, 156, 250, 252, 93, 41, 79, 85, 171, 243, 243, 250, 146, 102, 21, 109, 68, 106, 13, 160, 77, 216, 158, 194, 126, 161, 158, 183, 144, 26, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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