Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768b038ad0b0820cc3b5386e0bae88cf628fcf55e3afbf6a2775367d34d04c88

Tx prefix hash: 3803452e6e6fe0df153b68fa2dca14c813ff8ff2c12fd17db9bd81879b681232
Tx public key: 35b0fc983ecb2b675acd3b5cd133bf30dae6adf49da501f9e664fe81fd42cdb0
Timestamp: 1696107641 Timestamp [UCT]: 2023-09-30 21:00:41 Age [y:d:h:m:s]: 01:200:03:12:12
Block: 859682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404080 RingCT/type: yes/0
Extra: 0135b0fc983ecb2b675acd3b5cd133bf30dae6adf49da501f9e664fe81fd42cdb002110000000433af99f4000000000000000000

1 output(s) for total of 0.869994897000 dcy

stealth address amount amount idx
00: 7bb11c2cfd6127a22d638ef09f4507699b3758693a6c2b6041c2fce75f73d343 0.869994897000 1313922 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": 859692, "vin": [ { "gen": { "height": 859682 } } ], "vout": [ { "amount": 869994897, "target": { "key": "7bb11c2cfd6127a22d638ef09f4507699b3758693a6c2b6041c2fce75f73d343" } } ], "extra": [ 1, 53, 176, 252, 152, 62, 203, 43, 103, 90, 205, 59, 92, 209, 51, 191, 48, 218, 230, 173, 244, 157, 165, 1, 249, 230, 100, 254, 129, 253, 66, 205, 176, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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