Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df5a0340076f69cba94edd7e7e4742a298e691474876687b149aa143323ed152

Tx prefix hash: 2be3d19734f5e49bddd7fcf38e2c910679ef8fc19317df8909559ab8d7a27a67
Tx public key: 4cebf4ceb57c9062c7b309b3af1e0583424593b2ff0fb18f8b66ef23148929e9
Timestamp: 1750065045 Timestamp [UCT]: 2025-06-16 09:10:45 Age [y:d:h:m:s]: 00:157:13:16:35
Block: 1306139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110391 RingCT/type: yes/0
Extra: 014cebf4ceb57c9062c7b309b3af1e0583424593b2ff0fb18f8b66ef23148929e90211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8c847bd0cdb7a9c9e82334ad3c7d0a98dbe16379587be87e25a20b55deb89f0 0.600000000000 1793742 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": 1306149, "vin": [ { "gen": { "height": 1306139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c847bd0cdb7a9c9e82334ad3c7d0a98dbe16379587be87e25a20b55deb89f0" } } ], "extra": [ 1, 76, 235, 244, 206, 181, 124, 144, 98, 199, 179, 9, 179, 175, 30, 5, 131, 66, 69, 147, 178, 255, 15, 177, 143, 139, 102, 239, 35, 20, 137, 41, 233, 2, 17, 0, 0, 0, 2, 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