Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a529e3c80730ffa8ff8eac1ce899c9f8292e8d046baf076fdc9922693cdbcece

Tx prefix hash: b55efc68345535469ee940bdb501802089f097ac20d2a3715595ee07486a052f
Tx public key: 2d83eaf5e91f6746583fa7a3c944dfb2aa290e40e9ba1a903bc00f28f696baf0
Timestamp: 1773126267 Timestamp [UTC]: 2026-03-10 07:04:27 Age [y:d:h:m:s]: 00:255:17:49:40
Block: 1494619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188435 RingCT/type: yes/0
Extra: 012d83eaf5e91f6746583fa7a3c944dfb2aa290e40e9ba1a903bc00f28f696baf0021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2acc54535209a3dc6efdee4310a2e5637eed7179eae91e8b989b8832b21cccf4 0.000600000000 1984191 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": 1494629, "vin": [ { "gen": { "height": 1494619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2acc54535209a3dc6efdee4310a2e5637eed7179eae91e8b989b8832b21cccf4" } } ], "extra": [ 1, 45, 131, 234, 245, 233, 31, 103, 70, 88, 63, 167, 163, 201, 68, 223, 178, 170, 41, 14, 64, 233, 186, 26, 144, 59, 192, 15, 40, 246, 150, 186, 240, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: