Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d51fba9640a86634f7df7b5c9f8a06b77c9faae11633ea11bdc7b1f7aa5e081

Tx prefix hash: 54fbe378d5ef0833ba914b7b366515a7836fe6be1d1c9f9052b1abcd88ba8949
Tx public key: e242aaae8f44a388c22c01c61d6eaf43d98a1bb0375ae1d24d390bf3a0873342
Timestamp: 1784309555 Timestamp [UTC]: 2026-07-17 17:32:35 Age [y:d:h:m:s]: 00:125:06:13:33
Block: 1583904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98339 RingCT/type: yes/0
Extra: 01e242aaae8f44a388c22c01c61d6eaf43d98a1bb0375ae1d24d390bf3a0873342020874f9ad2fea1723c0

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78d397a98980ab40423af9f429af49bc2fdfe686ac3764aa4e1b1d25688e0ddd 0.000600000000 2073898 of 15 <4d>

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": 1583914, "vin": [ { "gen": { "height": 1583904 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "78d397a98980ab40423af9f429af49bc2fdfe686ac3764aa4e1b1d25688e0ddd", "view_tag": "4d" } } } ], "extra": [ 1, 226, 66, 170, 174, 143, 68, 163, 136, 194, 44, 1, 198, 29, 110, 175, 67, 217, 138, 27, 176, 55, 90, 225, 210, 77, 57, 11, 243, 160, 135, 51, 66, 2, 8, 116, 249, 173, 47, 234, 23, 35, 192 ], "rct_signatures": { "type": 0 } }


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