Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e46c85594ed16dca3d9d823f48f56489f61dfd74f7cf57b102afa622c8f5f9a4

Tx prefix hash: 56882e06581fe0c0a2b44855fc9a3b82efa581df38edca7be625dd8dab35c110
Tx public key: 59d742f17937230eeca7e326c19cf1f4ddf72c82adf4eff5d7b195789afc1cb9
Timestamp: 1707875985 Timestamp [UCT]: 2024-02-14 01:59:45 Age [y:d:h:m:s]: 00:335:05:53:33
Block: 957032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239995 RingCT/type: yes/0
Extra: 0159d742f17937230eeca7e326c19cf1f4ddf72c82adf4eff5d7b195789afc1cb90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c08c8d6337256229a37128b6ff9eae572af4b9e6dcb3c2beb70e2216ce55cd6 0.600000000000 1416346 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": 957042, "vin": [ { "gen": { "height": 957032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c08c8d6337256229a37128b6ff9eae572af4b9e6dcb3c2beb70e2216ce55cd6" } } ], "extra": [ 1, 89, 215, 66, 241, 121, 55, 35, 14, 236, 167, 227, 38, 193, 156, 241, 244, 221, 247, 44, 130, 173, 244, 239, 245, 215, 177, 149, 120, 154, 252, 28, 185, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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