Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07a1921e919e25a80355b5be06c093d3154048a4e81c4ec1ce04bc7b68f6f37

Tx prefix hash: c068daf27a0467868cc5981891b97e46001e421f0bacfb0c15767d213b1b40a7
Tx public key: e7695c5b175c3f1fbc45afa1d5176aba0c841210c4b0a9f8585f1f3e788f75e6
Timestamp: 1698373494 Timestamp [UCT]: 2023-10-27 02:24:54 Age [y:d:h:m:s]: 01:089:00:05:03
Block: 878477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324789 RingCT/type: yes/0
Extra: 01e7695c5b175c3f1fbc45afa1d5176aba0c841210c4b0a9f8585f1f3e788f75e60211000000034b8f5122000000000000000000

1 output(s) for total of 0.753773805000 dcy

stealth address amount amount idx
00: c2ea12cf87d2b46ce796b2c835f4e60bcdba419df3de45a1c02cf926567412d5 0.753773805000 1333925 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": 878487, "vin": [ { "gen": { "height": 878477 } } ], "vout": [ { "amount": 753773805, "target": { "key": "c2ea12cf87d2b46ce796b2c835f4e60bcdba419df3de45a1c02cf926567412d5" } } ], "extra": [ 1, 231, 105, 92, 91, 23, 92, 63, 31, 188, 69, 175, 161, 213, 23, 106, 186, 12, 132, 18, 16, 196, 176, 169, 248, 88, 95, 31, 62, 120, 143, 117, 230, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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