Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71d289b1862e49778db20b2313b7682e08d61c8aedae7d04087940daf5a2e90

Tx prefix hash: 8a4545ed731dc7fffe748d10ab99244f66c86546eb4376e4236d2f87780b8597
Tx public key: fcd4acc7e53d721f47f6a506a99cb6cb939dd38d38a13a985da718aa85e6f669
Timestamp: 1770757511 Timestamp [UTC]: 2026-02-10 21:05:11 Age [y:d:h:m:s]: 00:030:19:17:11
Block: 1475038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 22015 RingCT/type: yes/0
Extra: 01fcd4acc7e53d721f47f6a506a99cb6cb939dd38d38a13a985da718aa85e6f6690208c9773992940ce28e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 880d2dd5ca9ef0669e609d8c9133a2498d4bc13ae7f64f58c4286cecec4f7f8a 0.000600000000 1964336 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": 1475048, "vin": [ { "gen": { "height": 1475038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "880d2dd5ca9ef0669e609d8c9133a2498d4bc13ae7f64f58c4286cecec4f7f8a" } } ], "extra": [ 1, 252, 212, 172, 199, 229, 61, 114, 31, 71, 246, 165, 6, 169, 156, 182, 203, 147, 157, 211, 141, 56, 161, 58, 152, 93, 167, 24, 170, 133, 230, 246, 105, 2, 8, 201, 119, 57, 146, 148, 12, 226, 142 ], "rct_signatures": { "type": 0 } }


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