Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99643c47569abd8cd2884ed1b153ce9f0246f9c40025f6c725645f35980244ec

Tx prefix hash: 58961177de4932a62c43002eb0466bf0c7cdf106e3c74b9d20eee4779fb3087c
Tx public key: 1e1db1c57ca3b68f8d3564b0e28da755c74724db7bfcc0190b1788f0ed178c80
Timestamp: 1676800891 Timestamp [UCT]: 2023-02-19 10:01:31 Age [y:d:h:m:s]: 02:047:20:24:58
Block: 700294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555785 RingCT/type: yes/0
Extra: 011e1db1c57ca3b68f8d3564b0e28da755c74724db7bfcc0190b1788f0ed178c8002110000000275e3f0e9000000000000000000

1 output(s) for total of 2.935183011000 dcy

stealth address amount amount idx
00: b9fc5e73c6d36d097adc306910e5961846d0d4b9a965b6d1f07e45f24360997e 2.935183011000 1143731 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": 700304, "vin": [ { "gen": { "height": 700294 } } ], "vout": [ { "amount": 2935183011, "target": { "key": "b9fc5e73c6d36d097adc306910e5961846d0d4b9a965b6d1f07e45f24360997e" } } ], "extra": [ 1, 30, 29, 177, 197, 124, 163, 182, 143, 141, 53, 100, 176, 226, 141, 167, 85, 199, 71, 36, 219, 123, 252, 192, 25, 11, 23, 136, 240, 237, 23, 140, 128, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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