Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a322c15eaa0345c1c092eb50952b62e52ffed0097fec4dfaa43b7978adaffb6

Tx prefix hash: 12e8c7938ba618d61495ec9bfbce9af13714090330e5cb6af8939477d498592b
Tx public key: 6d56e1e9e1f8b032d02ea43fce957a2c4428a4da99df11b450f950199fde516d
Timestamp: 1774844087 Timestamp [UTC]: 2026-03-30 04:14:47 Age [y:d:h:m:s]: 00:044:23:39:49
Block: 1508838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24485 RingCT/type: yes/0
Extra: 016d56e1e9e1f8b032d02ea43fce957a2c4428a4da99df11b450f950199fde516d02110000000bf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d786a83ed6a7f9a185415c14b40b6f9fccc1c00d1cf05b3ddc778fdc31975312 0.000600000000 1998592 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": 1508848, "vin": [ { "gen": { "height": 1508838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d786a83ed6a7f9a185415c14b40b6f9fccc1c00d1cf05b3ddc778fdc31975312" } } ], "extra": [ 1, 109, 86, 225, 233, 225, 248, 176, 50, 208, 46, 164, 63, 206, 149, 122, 44, 68, 40, 164, 218, 153, 223, 17, 180, 80, 249, 80, 25, 159, 222, 81, 109, 2, 17, 0, 0, 0, 11, 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: