Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc3a4f712aab0277ac889a88ef60f098e0180c3061fd7a7608e58ede1e39e32

Tx prefix hash: 78ba1104d21e9511846c44b2d5a29d4c0fea9721eb9539f5f1fdb5ae8b869619
Tx public key: 1103b8f3d80dd22bdb555e095b97b219d42c8bd0d700672407ca6a35bbc396bd
Timestamp: 1701690809 Timestamp [UCT]: 2023-12-04 11:53:29 Age [y:d:h:m:s]: 01:124:17:26:11
Block: 905757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350285 RingCT/type: yes/0
Extra: 011103b8f3d80dd22bdb555e095b97b219d42c8bd0d700672407ca6a35bbc396bd021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.612140391000 dcy

stealth address amount amount idx
00: 7ef3376a4211f13554967c52bb8240885c761539ec104313d633bb091031eeb3 0.612140391000 1362672 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": 905767, "vin": [ { "gen": { "height": 905757 } } ], "vout": [ { "amount": 612140391, "target": { "key": "7ef3376a4211f13554967c52bb8240885c761539ec104313d633bb091031eeb3" } } ], "extra": [ 1, 17, 3, 184, 243, 216, 13, 210, 43, 219, 85, 94, 9, 91, 151, 178, 25, 212, 44, 139, 208, 215, 0, 103, 36, 7, 202, 106, 53, 187, 195, 150, 189, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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