Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2aaa8cdb13aa075e08076693833352e0d6fbc3dec0de6f8364969d7bac0b2e

Tx prefix hash: 2ae5633e56b51485068b3f3b3b0a550aad046ed083f0cc852b7df557aa97dc2e
Tx public key: 48e87c0e7fb00dc5e4046f7f03aa187c5100c866e0eb4c79503377236088d7a0
Timestamp: 1775205951 Timestamp [UTC]: 2026-04-03 08:45:51 Age [y:d:h:m:s]: 00:224:16:05:48
Block: 1511833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165946 RingCT/type: yes/0
Extra: 0148e87c0e7fb00dc5e4046f7f03aa187c5100c866e0eb4c79503377236088d7a0021100000004e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7d62a83e71329ea0bc26ab17124bb588401e51285b08bf6c0c21c5aabf3daffc 0.000600000000 2001627 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": 1511843, "vin": [ { "gen": { "height": 1511833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d62a83e71329ea0bc26ab17124bb588401e51285b08bf6c0c21c5aabf3daffc" } } ], "extra": [ 1, 72, 232, 124, 14, 127, 176, 13, 197, 228, 4, 111, 127, 3, 170, 24, 124, 81, 0, 200, 102, 224, 235, 76, 121, 80, 51, 119, 35, 96, 136, 215, 160, 2, 17, 0, 0, 0, 4, 227, 215, 220, 159, 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: