Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8724f97a56308da955649074ad2263d6116173c8f93e3319a1a61e3c1131ecf0

Tx prefix hash: a7d458ed2a7726c8068b4357de2f47ca3a8a768f08ecab9a079317a0dc421f4b
Tx public key: 02db13f4b1759492971bbee5c8ae857d3f91ab912b2efa46bd876b72ec5e76be
Timestamp: 1751157411 Timestamp [UCT]: 2025-06-29 00:36:51 Age [y:d:h:m:s]: 00:139:18:21:25
Block: 1314867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97987 RingCT/type: yes/0
Extra: 0102db13f4b1759492971bbee5c8ae857d3f91ab912b2efa46bd876b72ec5e76be021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899e38fffaf62a354d8871b4e22d129b55eb1a044f397adfa36e7b0137210922 0.600000000000 1802520 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": 1314877, "vin": [ { "gen": { "height": 1314867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899e38fffaf62a354d8871b4e22d129b55eb1a044f397adfa36e7b0137210922" } } ], "extra": [ 1, 2, 219, 19, 244, 177, 117, 148, 146, 151, 27, 190, 229, 200, 174, 133, 125, 63, 145, 171, 145, 43, 46, 250, 70, 189, 135, 107, 114, 236, 94, 118, 190, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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