Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e82bed697dba9d7f08343920ff9965888c4b86682e08429149d8f396cf00d0

Tx prefix hash: d614154f7d05201b13f693d97769fe14fee6df7c7f7a03694cca62076abc3da5
Tx public key: 9f206f499acacc8a6b20b8371e3239dc2f414964f8754ed1097c173539a8c595
Timestamp: 1695676011 Timestamp [UCT]: 2023-09-25 21:06:51 Age [y:d:h:m:s]: 01:199:01:50:49
Block: 856094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403354 RingCT/type: yes/0
Extra: 019f206f499acacc8a6b20b8371e3239dc2f414964f8754ed1097c173539a8c59502110000000233af99f4000000000000000000

1 output(s) for total of 0.894139424000 dcy

stealth address amount amount idx
00: dd38537b0f5d1a1aac4931b6a2232a7276a3b2b550169ac2edeab0de2af0b76d 0.894139424000 1310152 of 0

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": 856104, "vin": [ { "gen": { "height": 856094 } } ], "vout": [ { "amount": 894139424, "target": { "key": "dd38537b0f5d1a1aac4931b6a2232a7276a3b2b550169ac2edeab0de2af0b76d" } } ], "extra": [ 1, 159, 32, 111, 73, 154, 202, 204, 138, 107, 32, 184, 55, 30, 50, 57, 220, 47, 65, 73, 100, 248, 117, 78, 209, 9, 124, 23, 53, 57, 168, 197, 149, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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