Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ace554e1c5935e148cd56acc41e2a05a0bcf8407226b139bf8ba00d3f35d952

Tx prefix hash: 49ab862ca5ac78516512b2354e31cd577164eefca79b12f766299998c8cfc1cf
Tx public key: 1cad1a1d3d8ac2aa295da56cabfbb0652e330be9aabf108a7620d5077f060a08
Timestamp: 1742492940 Timestamp [UTC]: 2025-03-20 17:49:00 Age [y:d:h:m:s]: 01:247:05:30:56
Block: 1243578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440572 RingCT/type: yes/0
Extra: 011cad1a1d3d8ac2aa295da56cabfbb0652e330be9aabf108a7620d5077f060a08021100000001bfa77623000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 586fb04156a79b811f72943cf8b73aed0cf6f963c683eedb4f6a3a72e2c39f7c 0.000600000000 1730563 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": 1243588, "vin": [ { "gen": { "height": 1243578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "586fb04156a79b811f72943cf8b73aed0cf6f963c683eedb4f6a3a72e2c39f7c" } } ], "extra": [ 1, 28, 173, 26, 29, 61, 138, 194, 170, 41, 93, 165, 108, 171, 251, 176, 101, 46, 51, 11, 233, 170, 191, 16, 138, 118, 32, 213, 7, 127, 6, 10, 8, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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: