Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7d65c8e454512fc306e43a6a4bf4754a0505356defa785ed7206ba8f5aeacd

Tx prefix hash: 4f9edbb9f990aec07de33bf0ec0913e10c5008d4b4c386ed2da5dbcc785888dc
Tx public key: ce34e38779db61c84118b05a0e739d7acc1a0be240abc6849cb964ee61a981c6
Timestamp: 1690993762 Timestamp [UCT]: 2023-08-02 16:29:22 Age [y:d:h:m:s]: 01:245:14:41:51
Block: 817343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436626 RingCT/type: yes/0
Extra: 01ce34e38779db61c84118b05a0e739d7acc1a0be240abc6849cb964ee61a981c602110000000b75e3f0e9000000000000000000

1 output(s) for total of 1.201720446000 dcy

stealth address amount amount idx
00: 84b019ce44c28a91b970943967740d2e0f8dc174bd00fbc0aa7f943ead3097f3 1.201720446000 1269243 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": 817353, "vin": [ { "gen": { "height": 817343 } } ], "vout": [ { "amount": 1201720446, "target": { "key": "84b019ce44c28a91b970943967740d2e0f8dc174bd00fbc0aa7f943ead3097f3" } } ], "extra": [ 1, 206, 52, 227, 135, 121, 219, 97, 200, 65, 24, 176, 90, 14, 115, 157, 122, 204, 26, 11, 226, 64, 171, 198, 132, 156, 185, 100, 238, 97, 169, 129, 198, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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