Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d488fcd5fda4ba21eeb0ad0d6dd867a89db3d261308e5829865a7c971f6241

Tx prefix hash: 0ad2ab877bfe323a2e8f4e6f49846ce9584841e8f280c42e7473effb27159b7a
Tx public key: f8d3fdc4b266b56c0e84fb14e91b16669a390b5f3bbfd59a6d9f567208e55871
Timestamp: 1574544663 Timestamp [UTC]: 2019-11-23 21:31:03 Age [y:d:h:m:s]: 07:000:19:16:20
Block: 15926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1667568 RingCT/type: yes/0
Extra: 01f8d3fdc4b266b56c0e84fb14e91b16669a390b5f3bbfd59a6d9f567208e55871021100000009f95225a5000000000000000000

1 output(s) for total of 0.543539904332 xmr

stealth address amount amount idx tag
00: 441f686b40af2b847319720d07e0f54b30b14904e6e60ed5bffa61d6d0bd4fc8 0.543539904332 21779 of 0 -

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": 15936, "vin": [ { "gen": { "height": 15926 } } ], "vout": [ { "amount": 543539904332, "target": { "key": "441f686b40af2b847319720d07e0f54b30b14904e6e60ed5bffa61d6d0bd4fc8" } } ], "extra": [ 1, 248, 211, 253, 196, 178, 102, 181, 108, 14, 132, 251, 20, 233, 27, 22, 102, 154, 57, 11, 95, 59, 191, 213, 154, 109, 159, 86, 114, 8, 229, 88, 113, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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: