Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95c068a37697e68448bb38b1db407a8f1fa187e581c750fb86319e93c69a800

Tx prefix hash: 2d892bb6d3207c794678af3ee2727a74031727abc79053310e9b58833a8e068d
Tx public key: f2ea0db63d179a4650fa6d0f031cdfaec2833df25b6925ece5aa471b368d1da9
Timestamp: 1774106048 Timestamp [UTC]: 2026-03-21 15:14:08 Age [y:d:h:m:s]: 00:239:06:19:28
Block: 1502715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176459 RingCT/type: yes/0
Extra: 01f2ea0db63d179a4650fa6d0f031cdfaec2833df25b6925ece5aa471b368d1da902110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9951fbc9e70fbf76dbc74d56374377b574265972c34497d498a0d55d77316e17 0.000600000000 1992417 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": 1502725, "vin": [ { "gen": { "height": 1502715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9951fbc9e70fbf76dbc74d56374377b574265972c34497d498a0d55d77316e17" } } ], "extra": [ 1, 242, 234, 13, 182, 61, 23, 154, 70, 80, 250, 109, 15, 3, 28, 223, 174, 194, 131, 61, 242, 91, 105, 37, 236, 229, 170, 71, 27, 54, 141, 29, 169, 2, 17, 0, 0, 0, 12, 241, 136, 200, 168, 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: