Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2404f38b24d72bed6f9e71b8c16b33d7591fe66cb06f87ab2d2c649f1ad3e7

Tx prefix hash: 5f92306abed3a46b64aaca1297d07433bef9d1c0bf022c2e1243839275fb6177
Tx public key: bf57d4c5943063b861989a5f6254a89f71c71f97ced33426309d8f7e3603c54f
Timestamp: 1755839597 Timestamp [UTC]: 2025-08-22 05:13:17 Age [y:d:h:m:s]: 01:089:10:58:34
Block: 1351761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330242 RingCT/type: yes/0
Extra: 01bf57d4c5943063b861989a5f6254a89f71c71f97ced33426309d8f7e3603c54f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b92534f9d1ae45ebdb1c0f26018475b44e77f8556b4f56aedb2d38d11ccec204 0.000600000000 1839718 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": 1351771, "vin": [ { "gen": { "height": 1351761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b92534f9d1ae45ebdb1c0f26018475b44e77f8556b4f56aedb2d38d11ccec204" } } ], "extra": [ 1, 191, 87, 212, 197, 148, 48, 99, 184, 97, 152, 154, 95, 98, 84, 168, 159, 113, 199, 31, 151, 206, 211, 52, 38, 48, 157, 143, 126, 54, 3, 197, 79, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: