Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995eb2d1dbc3c4e09f3c222acb3c2da1f6b11b899208a8ec51c8bca4e2638ae3

Tx prefix hash: 6a2642cc2ba4fccbf8d8527cb3ae1105e0e44ff14c296e75726b32e6beb74d8f
Tx public key: 9d6632e1ecf61dbb43a2bdda5eb30ac25bce190a5a5a7e776a3e12204be9cc49
Timestamp: 1767307528 Timestamp [UTC]: 2026-01-01 22:45:28 Age [y:d:h:m:s]: 00:321:15:46:32
Block: 1446623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235329 RingCT/type: yes/0
Extra: 019d6632e1ecf61dbb43a2bdda5eb30ac25bce190a5a5a7e776a3e12204be9cc49021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 642fda8f274e1f90db474f3590ee9e5ee4643e60c26e24e7c9d07bc61c247ce2 0.000600000000 1935575 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": 1446633, "vin": [ { "gen": { "height": 1446623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642fda8f274e1f90db474f3590ee9e5ee4643e60c26e24e7c9d07bc61c247ce2" } } ], "extra": [ 1, 157, 102, 50, 225, 236, 246, 29, 187, 67, 162, 189, 218, 94, 179, 10, 194, 91, 206, 25, 10, 90, 90, 126, 119, 106, 62, 18, 32, 75, 233, 204, 73, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: