Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a0ca04627f822c3f6044ff6f0a010f46dac756e3a6aef3738bb79b0db3e1d8

Tx prefix hash: ef52f6bbe2a6a44b65313d405bf9e7a3866bc0cb1ab94b7722de3b1da6a4bcdc
Tx public key: 8c3a6eab5e0dca51787af81427396b0a2c338ac37433cf4d7ed044e5d9809aab
Timestamp: 1751913792 Timestamp [UTC]: 2025-07-07 18:43:12 Age [y:d:h:m:s]: 01:047:11:45:46
Block: 1320794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298963 RingCT/type: yes/0
Extra: 018c3a6eab5e0dca51787af81427396b0a2c338ac37433cf4d7ed044e5d9809aab021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f3a6fc345094f695d0d77432abc2a05182f3afdd5042c6ddfa13e4d4e4fa7f46 0.000600000000 1808495 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": 1320804, "vin": [ { "gen": { "height": 1320794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3a6fc345094f695d0d77432abc2a05182f3afdd5042c6ddfa13e4d4e4fa7f46" } } ], "extra": [ 1, 140, 58, 110, 171, 94, 13, 202, 81, 120, 122, 248, 20, 39, 57, 107, 10, 44, 51, 138, 195, 116, 51, 207, 77, 126, 208, 68, 229, 217, 128, 154, 171, 2, 17, 0, 0, 0, 1, 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: