Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cb421edcf02cbf4a7d353adbbcfd2e11ca8f54df00719452ab0562c5a4f10e7

Tx prefix hash: a016101761d21df58d88af7b8a9d31f4240b53172210b526a332075d1dca1d9e
Tx public key: e94e86a90326362c37562c53595820f6f2945e3c7fdd01c9cc59c4030ebb82a3
Timestamp: 1746218687 Timestamp [UCT]: 2025-05-02 20:44:47 Age [y:d:h:m:s]: 00:203:02:27:28
Block: 1274394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142873 RingCT/type: yes/0
Extra: 01e94e86a90326362c37562c53595820f6f2945e3c7fdd01c9cc59c4030ebb82a30211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fc515e621d2e978b59169f6b9325979d2fb4def6dad723faa411da5830b79a7 0.600000000000 1761689 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": 1274404, "vin": [ { "gen": { "height": 1274394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fc515e621d2e978b59169f6b9325979d2fb4def6dad723faa411da5830b79a7" } } ], "extra": [ 1, 233, 78, 134, 169, 3, 38, 54, 44, 55, 86, 44, 83, 89, 88, 32, 246, 242, 148, 94, 60, 127, 221, 1, 201, 204, 89, 196, 3, 14, 187, 130, 163, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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