Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d67667a57865cce5fda86d97586fe560b2bc80e2831aafb75116af0dd330726f

Tx prefix hash: 5ea0730bd43696024bb3ba6161740d3f7ccac0013e5182d033a36c63ea4b5832
Tx public key: 989d6bdeb7789b63c4b97ca7e1a9ad63ad3bc49b1558f6cedb4aa579ed9e9f58
Timestamp: 1658869915 Timestamp [UCT]: 2022-07-26 21:11:55 Age [y:d:h:m:s]: 02:307:09:38:50
Block: 552366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740955 RingCT/type: yes/0
Extra: 01989d6bdeb7789b63c4b97ca7e1a9ad63ad3bc49b1558f6cedb4aa579ed9e9f580211000000076570b1ef000000000000000000

1 output(s) for total of 9.073655216000 dcy

stealth address amount amount idx
00: 4555be8275f2d18b730482e62b26dc90afe1473371d2a2b0a17b1106d5f01527 9.073655216000 984068 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": 552376, "vin": [ { "gen": { "height": 552366 } } ], "vout": [ { "amount": 9073655216, "target": { "key": "4555be8275f2d18b730482e62b26dc90afe1473371d2a2b0a17b1106d5f01527" } } ], "extra": [ 1, 152, 157, 107, 222, 183, 120, 155, 99, 196, 185, 124, 167, 225, 169, 173, 99, 173, 59, 196, 155, 21, 88, 246, 206, 219, 74, 165, 121, 237, 158, 159, 88, 2, 17, 0, 0, 0, 7, 101, 112, 177, 239, 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