Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f922c1d9c2a07fe2efbb1445ba93d79012673e1586ac7a39bb48c071ab8393

Tx prefix hash: 66f9e148b013ecf3578192cfe324e142716d0df12b25644076b89b7367d873f5
Tx public key: 830ba4b4eae59dce8f682da0179c2568fb74f48020d53dac32f714d07f14ccd5
Timestamp: 1748051866 Timestamp [UTC]: 2025-05-24 01:57:46 Age [y:d:h:m:s]: 00:357:14:53:02
Block: 1289592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245643 RingCT/type: yes/0
Extra: 01830ba4b4eae59dce8f682da0179c2568fb74f48020d53dac32f714d07f14ccd50211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8c52da0d8038616d8b053f6f2e058a63bcb0f983962a9fa094d572e04ea0f585 0.000600000000 1777061 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": 1289602, "vin": [ { "gen": { "height": 1289592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c52da0d8038616d8b053f6f2e058a63bcb0f983962a9fa094d572e04ea0f585" } } ], "extra": [ 1, 131, 11, 164, 180, 234, 229, 157, 206, 143, 104, 45, 160, 23, 156, 37, 104, 251, 116, 244, 128, 32, 213, 61, 172, 50, 247, 20, 208, 127, 20, 204, 213, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: