Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9214054bd0198a733cb41af74dbc70c50b53ca3e9e783cdf4824e1d6bb1da86

Tx prefix hash: ddff663e8eb4f644c4b9c1c466789df7f190e0574e17a941105fef11cefcda53
Tx public key: ba5a48171dccae4b5e89e3a63c7780c96a80af2537d926241aa17771eb9fee42
Timestamp: 1754127755 Timestamp [UTC]: 2025-08-02 09:42:35 Age [y:d:h:m:s]: 01:110:03:23:43
Block: 1338649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344062 RingCT/type: yes/0
Extra: 01ba5a48171dccae4b5e89e3a63c7780c96a80af2537d926241aa17771eb9fee4202110000000bb2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 359677fc97c2cba7ca7a498509de0b9be9bcde4841d64468d898cc119ebb914c 0.000600000000 1826458 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": 1338659, "vin": [ { "gen": { "height": 1338649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "359677fc97c2cba7ca7a498509de0b9be9bcde4841d64468d898cc119ebb914c" } } ], "extra": [ 1, 186, 90, 72, 23, 29, 204, 174, 75, 94, 137, 227, 166, 60, 119, 128, 201, 106, 128, 175, 37, 55, 217, 38, 36, 26, 161, 119, 113, 235, 159, 238, 66, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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: