Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47be058e157f49137a768163302df3fa70949ce878817ef56b0224ebc891cf9a

Tx prefix hash: 4acd3e23ba6951ffe0e94718490461236c7835434ca0bd96b4872fd5c7e954ab
Tx public key: 637aed8cb88be29d1fc16ba2bd68f726b409c4cbc4b7e62a0f65139ea1f17af1
Timestamp: 1727833606 Timestamp [UCT]: 2024-10-02 01:46:46 Age [y:d:h:m:s]: 00:053:11:54:45
Block: 1122509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38213 RingCT/type: yes/0
Extra: 01637aed8cb88be29d1fc16ba2bd68f726b409c4cbc4b7e62a0f65139ea1f17af1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3c37b21929bd48771c8ee83d14fcd1eda2e3cdef59b3686ddfb27dffaa4002e 0.600000000000 1604960 of 15

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": 1122519, "vin": [ { "gen": { "height": 1122509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c37b21929bd48771c8ee83d14fcd1eda2e3cdef59b3686ddfb27dffaa4002e" } } ], "extra": [ 1, 99, 122, 237, 140, 184, 139, 226, 157, 31, 193, 107, 162, 189, 104, 247, 38, 180, 9, 196, 203, 196, 183, 230, 42, 15, 101, 19, 158, 161, 241, 122, 241, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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