Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2fee951e2e133c415d4802b9698b1e212bdb41b8003af35d9cc4c95866df05

Tx prefix hash: cc0943bfc5cb7b42f924825dfead45eb6edde5e775180250f4a23f611b56aa8b
Tx public key: 64a4ea3fe96bde0bd47f753e64821a1ff6fd17e8168f53e2217de73a24289aa0
Timestamp: 1769068274 Timestamp [UTC]: 2026-01-22 07:51:14 Age [y:d:h:m:s]: 00:112:04:40:49
Block: 1461066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72534 RingCT/type: yes/0
Extra: 0164a4ea3fe96bde0bd47f753e64821a1ff6fd17e8168f53e2217de73a24289aa0021100000004215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4794fba3aefd3a5c65c23ba494f1aa86244acde9ef23be160111831ddfd305b 0.000600000000 1950246 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": 1461076, "vin": [ { "gen": { "height": 1461066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4794fba3aefd3a5c65c23ba494f1aa86244acde9ef23be160111831ddfd305b" } } ], "extra": [ 1, 100, 164, 234, 63, 233, 107, 222, 11, 212, 127, 117, 62, 100, 130, 26, 31, 246, 253, 23, 232, 22, 143, 83, 226, 33, 125, 231, 58, 36, 40, 154, 160, 2, 17, 0, 0, 0, 4, 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: