Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed9ff13a232528e7b162df84fb74353a91fe46c0ada2832dcbda4caff5423a4e

Tx prefix hash: c7fe94435779ed0cd2028b046cec69877308d2b6b623f237ad2f7ac069ffb3ab
Tx public key: 2cc791f021b2413bf48534309d923d63a7a480e00a43aebefed62e734fc35929
Timestamp: 1769448274 Timestamp [UTC]: 2026-01-26 17:24:34 Age [y:d:h:m:s]: 00:293:07:24:05
Block: 1464177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215099 RingCT/type: yes/0
Extra: 012cc791f021b2413bf48534309d923d63a7a480e00a43aebefed62e734fc3592902110000000549d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 979e1b4ec18751510e425f128b6b9f6e47a5321bcfd7ee007715b7040fe09e9b 0.000600000000 1953401 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": 1464187, "vin": [ { "gen": { "height": 1464177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979e1b4ec18751510e425f128b6b9f6e47a5321bcfd7ee007715b7040fe09e9b" } } ], "extra": [ 1, 44, 199, 145, 240, 33, 178, 65, 59, 244, 133, 52, 48, 157, 146, 61, 99, 167, 164, 128, 224, 10, 67, 174, 190, 254, 214, 46, 115, 79, 195, 89, 41, 2, 17, 0, 0, 0, 5, 73, 215, 62, 152, 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: