Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20262d4f214269596751793bc7fd5cfc90cc47ca99d3da007dcaabc14edfb2be

Tx prefix hash: 859745220b944f601417c784d6ad46987996d95de3a92fc9bd25090ad0bf4cfe
Tx public key: 8eab2e5a4e262b79f660b29440f403d6d5e957a43e8f416c84d1e5fcacb83034
Timestamp: 1629257242 Timestamp [UCT]: 2021-08-18 03:27:22 Age [y:d:h:m:s]: 03:137:03:25:08
Block: 316282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871414 RingCT/type: yes/0
Extra: 018eab2e5a4e262b79f660b29440f403d6d5e957a43e8f416c84d1e5fcacb83034021100000084e084ab86000000000000000000

1 output(s) for total of 54.961552048000 dcy

stealth address amount amount idx
00: dffe9d5a3f5f4b28ba0b2c1f2e1f4c7549f8610fc516e6955f848d8ab33523bd 54.961552048000 658037 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": 316292, "vin": [ { "gen": { "height": 316282 } } ], "vout": [ { "amount": 54961552048, "target": { "key": "dffe9d5a3f5f4b28ba0b2c1f2e1f4c7549f8610fc516e6955f848d8ab33523bd" } } ], "extra": [ 1, 142, 171, 46, 90, 78, 38, 43, 121, 246, 96, 178, 148, 64, 244, 3, 214, 213, 233, 87, 164, 62, 143, 65, 108, 132, 209, 229, 252, 172, 184, 48, 52, 2, 17, 0, 0, 0, 132, 224, 132, 171, 134, 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