Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c377ecfd52ad6c0efa8b27e9efe2a04d36833ef9df3286499bb2532bef9f541

Tx prefix hash: 9cdf89ca0e687435e66db713f753dff1d8afe0a72cb9cc7b892ae1fe87102404
Tx public key: 49fb121415fb7e71041365e6e839e9b57e48f8dbe6f51bd187f82154dce92e54
Timestamp: 1584771896 Timestamp [UCT]: 2020-03-21 06:24:56 Age [y:d:h:m:s]: 04:279:23:02:06
Block: 86400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096262 RingCT/type: yes/0
Extra: 0149fb121415fb7e71041365e6e839e9b57e48f8dbe6f51bd187f82154dce92e540211000000058e8a0ce2000000000000000000

1 output(s) for total of 317.483905589000 dcy

stealth address amount amount idx
00: ef65c533c31a4fa2b382d67f9de1fc55a77897a941de89ca5a1cbe0f14c489c7 317.483905589000 155844 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": 86410, "vin": [ { "gen": { "height": 86400 } } ], "vout": [ { "amount": 317483905589, "target": { "key": "ef65c533c31a4fa2b382d67f9de1fc55a77897a941de89ca5a1cbe0f14c489c7" } } ], "extra": [ 1, 73, 251, 18, 20, 21, 251, 126, 113, 4, 19, 101, 230, 232, 57, 233, 181, 126, 72, 248, 219, 230, 245, 27, 209, 135, 248, 33, 84, 220, 233, 46, 84, 2, 17, 0, 0, 0, 5, 142, 138, 12, 226, 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