Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88bca360e27b714b1d4e513f33e1b07836c5d31babd396fae1cdd4e43f57a5f8

Tx prefix hash: 029550f04a96fccc960c929138a95d7b3934bed5cc5638e80725a2ac1ac9a77a
Tx public key: c71d829d83d3c304743896d0527d1b83f4e0dba78317affe67dc4423ce27f619
Timestamp: 1712593036 Timestamp [UCT]: 2024-04-08 16:17:16 Age [y:d:h:m:s]: 01:264:02:14:52
Block: 996114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447518 RingCT/type: yes/0
Extra: 01c71d829d83d3c304743896d0527d1b83f4e0dba78317affe67dc4423ce27f61902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08ce67097190fa051ed1f3f54487808e9a352b5f47dc2add9d9413a6de31acd7 0.600000000000 1456530 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": 996124, "vin": [ { "gen": { "height": 996114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08ce67097190fa051ed1f3f54487808e9a352b5f47dc2add9d9413a6de31acd7" } } ], "extra": [ 1, 199, 29, 130, 157, 131, 211, 195, 4, 116, 56, 150, 208, 82, 125, 27, 131, 244, 224, 219, 167, 131, 23, 175, 254, 103, 220, 68, 35, 206, 39, 246, 25, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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