Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6db3800f2470dc3caa90ede3c628aa7fe67b7cc86dbfcf1cc0dbd12f4d9bfd85

Tx prefix hash: 1415796e63ea9d4a4f043705179d861f109896a24440a05f96d0efff0bfefd1d
Tx public key: 4caeedc87c121d1385eb6ac31f955935479f7c689e814a17f78a7027635b41ba
Timestamp: 1751388541 Timestamp [UCT]: 2025-07-01 16:49:01 Age [y:d:h:m:s]: 00:131:05:16:14
Block: 1316660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91997 RingCT/type: yes/0
Extra: 014caeedc87c121d1385eb6ac31f955935479f7c689e814a17f78a7027635b41ba02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 716b92a5ed7de63461e50dd2dc7d55b8e4e3f0f61f3d0c96b19ddcbf4b37363a 0.600000000000 1804321 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": 1316670, "vin": [ { "gen": { "height": 1316660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "716b92a5ed7de63461e50dd2dc7d55b8e4e3f0f61f3d0c96b19ddcbf4b37363a" } } ], "extra": [ 1, 76, 174, 237, 200, 124, 18, 29, 19, 133, 235, 106, 195, 31, 149, 89, 53, 71, 159, 124, 104, 158, 129, 74, 23, 247, 138, 112, 39, 99, 91, 65, 186, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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