Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1dd9707a7c87517cd05e41026d5fe4512a10886dfed509663b0a6cd2b581e16

Tx prefix hash: c53dcaa53ab0d9975988ebf1467b4b3c45880b544105f9a979afa5c56aaba7cd
Tx public key: bbc709b0e11f5bc7de06bcb8a0331a0bb9b79f63197f10b96d6f48d985dc6e9c
Timestamp: 1576643337 Timestamp [UTC]: 2019-12-18 04:28:57 Age [y:d:h:m:s]: 06:250:16:47:53
Block: 28164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1591318 RingCT/type: yes/0
Extra: 01bbc709b0e11f5bc7de06bcb8a0331a0bb9b79f63197f10b96d6f48d985dc6e9c021100000012ad433a0b000000000000000000

1 output(s) for total of 0.495087363392 xmr

stealth address amount amount idx tag
00: 762fcdc42c89d656ca0324cc2178f1ac9ab0fbd5b5c718e9b8d4845264f1e8d3 0.495087363392 46694 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 dinastycoin-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": 28174, "vin": [ { "gen": { "height": 28164 } } ], "vout": [ { "amount": 495087363392, "target": { "key": "762fcdc42c89d656ca0324cc2178f1ac9ab0fbd5b5c718e9b8d4845264f1e8d3" } } ], "extra": [ 1, 187, 199, 9, 176, 225, 31, 91, 199, 222, 6, 188, 184, 160, 51, 26, 11, 185, 183, 159, 99, 25, 127, 16, 185, 109, 111, 72, 217, 133, 220, 110, 156, 2, 17, 0, 0, 0, 18, 173, 67, 58, 11, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: