Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be3f7a4927ee7f414e1e70952b2cd8b9419b99fffb3b0514cb9b907a4ef0e4cc

Tx prefix hash: dc7075ec55091b832a30c59f12fd5449011e953e0debd6b29b53ac2304c88846
Tx public key: d19309bb03749036e5df618e76799097d47b1b090346614de6415855737e254e
Timestamp: 1748119046 Timestamp [UTC]: 2025-05-24 20:37:26 Age [y:d:h:m:s]: 01:176:17:24:12
Block: 1290135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390289 RingCT/type: yes/0
Extra: 01d19309bb03749036e5df618e76799097d47b1b090346614de6415855737e254e021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 821d58c730f92d244cc004518b7a4d3d6612f9a0f4382a6c0aab30cd9541b45b 0.000600000000 1777604 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": 1290145, "vin": [ { "gen": { "height": 1290135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "821d58c730f92d244cc004518b7a4d3d6612f9a0f4382a6c0aab30cd9541b45b" } } ], "extra": [ 1, 209, 147, 9, 187, 3, 116, 144, 54, 229, 223, 97, 142, 118, 121, 144, 151, 212, 123, 27, 9, 3, 70, 97, 77, 230, 65, 88, 85, 115, 126, 37, 78, 2, 17, 0, 0, 0, 2, 161, 29, 186, 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: