Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0370c813b56c8abba332c8fc5efb0b923bd7e7c46a22fa9a6bf29b10e34850b0

Tx prefix hash: 7f757ed36277caacf8bb5cc958686179a302ccd85a1d046682d6da1f2ff19075
Tx public key: 79e554ce1a65202e89a69fcbc3ee19b4c22e07fad773ae3f59ffc197199557f8
Timestamp: 1750036685 Timestamp [UTC]: 2025-06-16 01:18:05 Age [y:d:h:m:s]: 01:155:18:50:44
Block: 1305908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375450 RingCT/type: yes/0
Extra: 0179e554ce1a65202e89a69fcbc3ee19b4c22e07fad773ae3f59ffc197199557f8021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 634d3f90ff098f1d4b722241be0dcc1fbdb9a733cd75ce9fe51547b0539d6346 0.000600000000 1793511 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": 1305918, "vin": [ { "gen": { "height": 1305908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "634d3f90ff098f1d4b722241be0dcc1fbdb9a733cd75ce9fe51547b0539d6346" } } ], "extra": [ 1, 121, 229, 84, 206, 26, 101, 32, 46, 137, 166, 159, 203, 195, 238, 25, 180, 194, 46, 7, 250, 215, 115, 174, 63, 89, 255, 193, 151, 25, 149, 87, 248, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: