Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bee65a0c6bf3c7c904e23510ea73b1daa4cfed20012d34770192ce5bde40e7bb

Tx prefix hash: 9a9cfb64121af7c697d365ce3bf1183cf13c3b3d818d408ae5a4af44e369c6ce
Tx public key: d9da0d92bf49ec851d418d1bebd80ec78ca3fc62065b48bfc76c2af3cfd79d1d
Timestamp: 1750367392 Timestamp [UTC]: 2025-06-19 21:09:52 Age [y:d:h:m:s]: 01:146:11:53:52
Block: 1308607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368668 RingCT/type: yes/0
Extra: 01d9da0d92bf49ec851d418d1bebd80ec78ca3fc62065b48bfc76c2af3cfd79d1d021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 58ae0cd322e4b5690da1c0c5f6c1a7454b62c3888751ee27116960d10e125040 0.000600000000 1796220 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": 1308617, "vin": [ { "gen": { "height": 1308607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58ae0cd322e4b5690da1c0c5f6c1a7454b62c3888751ee27116960d10e125040" } } ], "extra": [ 1, 217, 218, 13, 146, 191, 73, 236, 133, 29, 65, 141, 27, 235, 216, 14, 199, 140, 163, 252, 98, 6, 91, 72, 191, 199, 108, 42, 243, 207, 215, 157, 29, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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: