Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d434029fff3e001e453416fa1a0a7d661d4aff1237fb2e910b95e1e6c6e3b636

Tx prefix hash: 73f4203095818e3e031ddf0e545198101666b43983884c80490f931fa2e1475a
Tx public key: f07194347e61d7650972f56b62bdb046bb519b1a4988a269f48ecfe0a2858211
Timestamp: 1768320337 Timestamp [UTC]: 2026-01-13 16:05:37 Age [y:d:h:m:s]: 00:311:07:12:17
Block: 1454865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228135 RingCT/type: yes/0
Extra: 01f07194347e61d7650972f56b62bdb046bb519b1a4988a269f48ecfe0a285821102110000000749d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f7f7c5a8f79a9604c8c077dd49ee6175009640976fc73b2e2ed1118184fdaf7d 0.000600000000 1943959 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": 1454875, "vin": [ { "gen": { "height": 1454865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7f7c5a8f79a9604c8c077dd49ee6175009640976fc73b2e2ed1118184fdaf7d" } } ], "extra": [ 1, 240, 113, 148, 52, 126, 97, 215, 101, 9, 114, 245, 107, 98, 189, 176, 70, 187, 81, 155, 26, 73, 136, 162, 105, 244, 142, 207, 224, 162, 133, 130, 17, 2, 17, 0, 0, 0, 7, 73, 215, 62, 152, 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: