Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f16c53e66f218b8071b60d05bbaa09ef40a41fc60f41d9a373b56cb95aa16b

Tx prefix hash: 8e6a89d03fc535efa45314570d0c3299d081cb02d93f123fac0719f724d2634e
Tx public key: 70ca8ad0a1526f4877ef2fe4c211df983bb14fde893effb22c1d9965b355eb59
Timestamp: 1699728703 Timestamp [UCT]: 2023-11-11 18:51:43 Age [y:d:h:m:s]: 01:126:17:18:34
Block: 889495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351769 RingCT/type: yes/0
Extra: 0170ca8ad0a1526f4877ef2fe4c211df983bb14fde893effb22c1d9965b355eb590211000000014b8f5122000000000000000000

1 output(s) for total of 0.693010929000 dcy

stealth address amount amount idx
00: 8ad32cc088d73d098f49f6d0e30bc3440d9a7a115b07559d05ebbcb7aa51045c 0.693010929000 1345496 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": 889505, "vin": [ { "gen": { "height": 889495 } } ], "vout": [ { "amount": 693010929, "target": { "key": "8ad32cc088d73d098f49f6d0e30bc3440d9a7a115b07559d05ebbcb7aa51045c" } } ], "extra": [ 1, 112, 202, 138, 208, 161, 82, 111, 72, 119, 239, 47, 228, 194, 17, 223, 152, 59, 177, 79, 222, 137, 62, 255, 178, 44, 29, 153, 101, 179, 85, 235, 89, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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