Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecbe238b99ddb904cc4f8635f651429f94117d7a46038cfc69c56f12e954b72a

Tx prefix hash: 74bfe7b4bc04a584769f94c04dd2eecd96c70d043bbf5490c7bb2e46d3ee0927
Tx public key: f450311cebde0be5e24d10e8d644f8bcb47633d748da221ea12c0a3de8d4fa80
Timestamp: 1772097225 Timestamp [UTC]: 2026-02-26 09:13:45 Age [y:d:h:m:s]: 00:269:14:38:00
Block: 1486094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198056 RingCT/type: yes/0
Extra: 01f450311cebde0be5e24d10e8d644f8bcb47633d748da221ea12c0a3de8d4fa80021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c37e67d13f12fb0ed01ea1b9aafda5fb74d41643984ef28aa448b93ff9bf60e4 0.000600000000 1975538 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": 1486104, "vin": [ { "gen": { "height": 1486094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c37e67d13f12fb0ed01ea1b9aafda5fb74d41643984ef28aa448b93ff9bf60e4" } } ], "extra": [ 1, 244, 80, 49, 28, 235, 222, 11, 229, 226, 77, 16, 232, 214, 68, 248, 188, 180, 118, 51, 215, 72, 218, 34, 30, 161, 44, 10, 61, 232, 212, 250, 128, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: