Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411410319587aa5624c150f11bb8150bf90befbb65b87dd38dc4cd3da21db62b

Tx prefix hash: 425363406286d00c734a243ec85a8e29df7d57b605322ec8c093e920ec9ebeb5
Tx public key: 32f50e7f165b38b6589f864e5983b60434de5ab06770f82b4cf8aa2aa5c820f7
Timestamp: 1743949305 Timestamp [UTC]: 2025-04-06 14:21:45 Age [y:d:h:m:s]: 01:224:13:04:38
Block: 1255596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424512 RingCT/type: yes/0
Extra: 0132f50e7f165b38b6589f864e5983b60434de5ab06770f82b4cf8aa2aa5c820f70211000000056c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 18b524a83ad656de73d7bed4292cfebb8e77d0d77b1482363af220e1de2a6f48 0.000600000000 1742701 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": 1255606, "vin": [ { "gen": { "height": 1255596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18b524a83ad656de73d7bed4292cfebb8e77d0d77b1482363af220e1de2a6f48" } } ], "extra": [ 1, 50, 245, 14, 127, 22, 91, 56, 182, 88, 159, 134, 78, 89, 131, 182, 4, 52, 222, 90, 176, 103, 112, 248, 43, 76, 248, 170, 42, 165, 200, 32, 247, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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: