Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cab93a53e5daa5469226d25f5fed11179718462c8297909ad3d039242ffa948b

Tx prefix hash: d6fab7520a74bf73df98f8f91b9476ad5acb2736b216b5f2e4b2a3fd68b9c802
Tx public key: d3edb04760b0e11b581d4d9ae9de3d4175db78aeeeee9df199b45e88d3a74310
Timestamp: 1714674216 Timestamp [UCT]: 2024-05-02 18:23:36 Age [y:d:h:m:s]: 00:340:09:02:09
Block: 1013408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243291 RingCT/type: yes/0
Extra: 01d3edb04760b0e11b581d4d9ae9de3d4175db78aeeeee9df199b45e88d3a743100211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09e5716f20b64b707b986a1bcb846669dbf2b96cb2581ecdeed288ad12e01827 0.600000000000 1476215 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": 1013418, "vin": [ { "gen": { "height": 1013408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09e5716f20b64b707b986a1bcb846669dbf2b96cb2581ecdeed288ad12e01827" } } ], "extra": [ 1, 211, 237, 176, 71, 96, 176, 225, 27, 88, 29, 77, 154, 233, 222, 61, 65, 117, 219, 120, 174, 238, 238, 157, 241, 153, 180, 94, 136, 211, 167, 67, 16, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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