Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c1befb0963d4c11953d4bc34ec0a378e16f25e73b10f101f49b1ad5a6aa39f

Tx prefix hash: 30d0ab33f33abea1d94b654f36fc4513da248c8091d0b21859f7709cbae61085
Tx public key: c1886a620ddd418ed0f1d5a8de79d941103a0a7adcdc288c524960eb166a501b
Timestamp: 1784078385 Timestamp [UTC]: 2026-07-15 01:19:45 Age [y:d:h:m:s]: 00:130:15:11:53
Block: 1582531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 100963 RingCT/type: yes/0
Extra: 01c1886a620ddd418ed0f1d5a8de79d941103a0a7adcdc288c524960eb166a501b02082f0363bbca8cc2d5

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4db6a9015e493300e4c7b817704a5aa0b7caaf92d14ad1889c951248c1d7b87e 0.000600000000 2072525 of 15 <68>

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": 1582541, "vin": [ { "gen": { "height": 1582531 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4db6a9015e493300e4c7b817704a5aa0b7caaf92d14ad1889c951248c1d7b87e", "view_tag": "68" } } } ], "extra": [ 1, 193, 136, 106, 98, 13, 221, 65, 142, 208, 241, 213, 168, 222, 121, 217, 65, 16, 58, 10, 122, 220, 220, 40, 140, 82, 73, 96, 235, 22, 106, 80, 27, 2, 8, 47, 3, 99, 187, 202, 140, 194, 213 ], "rct_signatures": { "type": 0 } }


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