Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516ac948d65d75cb08e91b932d467e8546fc265264e2cfca2e1d4a789efc85b3

Tx prefix hash: 7fbcc7a24fb2d5ae8b798807319306f7d308792c0154fe24b659df12bd967d2c
Tx public key: 8b9ce50a0c8b788d4ba3b06f9a22645c9737d86ddc270759cc857b6183973ab9
Timestamp: 1773513296 Timestamp [UTC]: 2026-03-14 18:34:56 Age [y:d:h:m:s]: 00:245:06:38:39
Block: 1497835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180694 RingCT/type: yes/0
Extra: 018b9ce50a0c8b788d4ba3b06f9a22645c9737d86ddc270759cc857b6183973ab9021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc62a827bddfda3a0491b8008f3c8b4a7d3572d15862272aa06b04d2be69dc41 0.000600000000 1987477 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 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": 1497845, "vin": [ { "gen": { "height": 1497835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc62a827bddfda3a0491b8008f3c8b4a7d3572d15862272aa06b04d2be69dc41" } } ], "extra": [ 1, 139, 156, 229, 10, 12, 139, 120, 141, 75, 163, 176, 111, 154, 34, 100, 92, 151, 55, 216, 109, 220, 39, 7, 89, 204, 133, 123, 97, 131, 151, 58, 185, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: