Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8eb11e18bbc83b7254106c3cc2eb3d2389b6806c3d3e3147df0f3f19f0d4c8

Tx prefix hash: 1e98fd2af151edaf402bab76a69560343bb422d7943d8689cbaef799376ebecc
Tx public key: 4a5d7ae221cdcf7100aae91fa5a78ed7a6941992158480b44a0a631c20e2caec
Timestamp: 1767641471 Timestamp [UTC]: 2026-01-05 19:31:11 Age [y:d:h:m:s]: 00:314:00:38:50
Block: 1449407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229724 RingCT/type: yes/0
Extra: 014a5d7ae221cdcf7100aae91fa5a78ed7a6941992158480b44a0a631c20e2caec021100000014215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e8e16c0bef81910b4de944065d6203c4194d4c513d5c79efce5770a99ede4fc9 0.000600000000 1938391 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": 1449417, "vin": [ { "gen": { "height": 1449407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8e16c0bef81910b4de944065d6203c4194d4c513d5c79efce5770a99ede4fc9" } } ], "extra": [ 1, 74, 93, 122, 226, 33, 205, 207, 113, 0, 170, 233, 31, 165, 167, 142, 215, 166, 148, 25, 146, 21, 132, 128, 180, 74, 10, 99, 28, 32, 226, 202, 236, 2, 17, 0, 0, 0, 20, 33, 91, 191, 137, 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: