Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624365f8e68e24278331015c44e2d9135fae60e7c2ead1d7f691dea180d91789

Tx prefix hash: e8634ea4f13080b32b502c118205c0fb604be1e07b9449c1f19b9cde779a2f1c
Tx public key: 2cfe8d32ec83766639c0e89ee6a61c71777ec745270045cc965aa3e3aca34cb1
Timestamp: 1745139594 Timestamp [UCT]: 2025-04-20 08:59:54 Age [y:d:h:m:s]: 00:022:11:17:31
Block: 1265462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16074 RingCT/type: yes/0
Extra: 012cfe8d32ec83766639c0e89ee6a61c71777ec745270045cc965aa3e3aca34cb10211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3632dff9ce37c98447836f897634f0d7f1fc0fff1671b58ff1d0a45b59f1f1f 0.600000000000 1752671 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": 1265472, "vin": [ { "gen": { "height": 1265462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3632dff9ce37c98447836f897634f0d7f1fc0fff1671b58ff1d0a45b59f1f1f" } } ], "extra": [ 1, 44, 254, 141, 50, 236, 131, 118, 102, 57, 192, 232, 158, 230, 166, 28, 113, 119, 126, 199, 69, 39, 0, 69, 204, 150, 90, 163, 227, 172, 163, 76, 177, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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