Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dd4dbb26500f05a5dcf86bbcb100fe95083a4dc0c44beea64ae31eb83c6f105

Tx prefix hash: e18ad3d949b03077b5fad8c2bc632f72db49135f984c09b7dfb42aa7b7cdc089
Tx public key: 5b7378279a14b5082e3e6a0a57fb48ad4cd5daeee5cffb992e8d1b0abf1b3687
Timestamp: 1791995387 Timestamp [UTC]: 2026-10-14 16:29:47 Age [y:d:h:m:s]: 00:033:07:34:46
Block: 1654400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 25610 RingCT/type: yes/0
Extra: 015b7378279a14b5082e3e6a0a57fb48ad4cd5daeee5cffb992e8d1b0abf1b3687

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd7be75c2dd04e60b0a73cd4b5abea1e3abb6c788b0997b077c81ae7f4ba7d3e 0.000600000000 2145110 of 15 <84>

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": 1654410, "vin": [ { "gen": { "height": 1654400 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "dd7be75c2dd04e60b0a73cd4b5abea1e3abb6c788b0997b077c81ae7f4ba7d3e", "view_tag": "84" } } } ], "extra": [ 1, 91, 115, 120, 39, 154, 20, 181, 8, 46, 62, 106, 10, 87, 251, 72, 173, 76, 213, 218, 238, 229, 207, 251, 153, 46, 141, 27, 10, 191, 27, 54, 135 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: