Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4e2dd64bf06c6c00a69c51a119b02e9a96e5889a0d9e108c8b244c509a42b98

Tx prefix hash: a361a38e774f9c5c932d278d51a52f0c561f36348f5797bcb37c92408bfbb8f7
Tx public key: fbb20a36a87abe569f531f70b4a545839678ab0512db36af80d750c414696510
Timestamp: 1696095898 Timestamp [UCT]: 2023-09-30 17:44:58 Age [y:d:h:m:s]: 01:147:18:58:24
Block: 859577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366646 RingCT/type: yes/0
Extra: 01fbb20a36a87abe569f531f70b4a545839678ab0512db36af80d750c4146965100211000000014b8f5122000000000000000000

1 output(s) for total of 0.870692120000 dcy

stealth address amount amount idx
00: 281da373e7a8a4593663fe5ed2e4f90f031ad61add294c3c66da1795c24f3e64 0.870692120000 1313809 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": 859587, "vin": [ { "gen": { "height": 859577 } } ], "vout": [ { "amount": 870692120, "target": { "key": "281da373e7a8a4593663fe5ed2e4f90f031ad61add294c3c66da1795c24f3e64" } } ], "extra": [ 1, 251, 178, 10, 54, 168, 122, 190, 86, 159, 83, 31, 112, 180, 165, 69, 131, 150, 120, 171, 5, 18, 219, 54, 175, 128, 215, 80, 196, 20, 105, 101, 16, 2, 17, 0, 0, 0, 1, 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