Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeee06b06dcaf220d4a9fea642c64e58cd17194ed29bf1ef6e252fa741cfd820

Tx prefix hash: 2177fb3a6f4dd1ab6c1b01a74bf12db1d68d4dce4714ea4961924c818b325845
Tx public key: 259e7968b327b823d7f18e949c916e7760e939b5477e60a7ec2ca18a9c9527f0
Timestamp: 1694220077 Timestamp [UCT]: 2023-09-09 00:41:17 Age [y:d:h:m:s]: 01:220:05:52:35
Block: 844009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418521 RingCT/type: yes/0
Extra: 01259e7968b327b823d7f18e949c916e7760e939b5477e60a7ec2ca18a9c9527f0021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.980500645000 dcy

stealth address amount amount idx
00: 8aa15d9d427fa97d05cb4a4ef14315a3b9efb8add2043e122fca02c61a130060 0.980500645000 1297291 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": 844019, "vin": [ { "gen": { "height": 844009 } } ], "vout": [ { "amount": 980500645, "target": { "key": "8aa15d9d427fa97d05cb4a4ef14315a3b9efb8add2043e122fca02c61a130060" } } ], "extra": [ 1, 37, 158, 121, 104, 179, 39, 184, 35, 215, 241, 142, 148, 156, 145, 110, 119, 96, 233, 57, 181, 71, 126, 96, 167, 236, 44, 161, 138, 156, 149, 39, 240, 2, 17, 0, 0, 0, 4, 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