Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c1855364f350f67f79c0adec8d3a2ea68696aca5cfaa39caf8d0e006e67916c

Tx prefix hash: 92f9b0f1eb926cc3e7e55c4aeaeea49c2cb0f07cde3824ee1fa16af9d356b404
Tx public key: a1482e170f60d975ae8b5dc95195f55d8ad6a6c7479168e6e46c473d4ab8704c
Timestamp: 1754454055 Timestamp [UCT]: 2025-08-06 04:20:55 Age [y:d:h:m:s]: 00:063:19:35:28
Block: 1341240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44550 RingCT/type: yes/0
Extra: 01a1482e170f60d975ae8b5dc95195f55d8ad6a6c7479168e6e46c473d4ab8704c021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc9ff6d930b826a051afe7e0a5700b010ade5b0d5008a3ab91f7fe228a31fe66 0.600000000000 1829063 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": 1341250, "vin": [ { "gen": { "height": 1341240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc9ff6d930b826a051afe7e0a5700b010ade5b0d5008a3ab91f7fe228a31fe66" } } ], "extra": [ 1, 161, 72, 46, 23, 15, 96, 217, 117, 174, 139, 93, 201, 81, 149, 245, 93, 138, 214, 166, 199, 71, 145, 104, 230, 228, 108, 71, 61, 74, 184, 112, 76, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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